Or spacetime is that aether. This is like some dusty books have been claiming that there's an invisible fluid substance around us that supports life, then when science discovers oxygen, it says "See? There is no invisible ether or anything like that around us, only atoms."
I've seen messy devs who absolutely can't articulate themselves, to the extent that when they tried, everybody else would keep awkward silence, and yet they made 60k/month.
And those small companies would be able to compensate the difference in pay with "partner" status, i.e. making an employee an unfireable stakeholder that can live off profits by the time he or she turns say 45, but owners of said small companies are too greedy for that. I'd argue that opportunistic at-employement with 500k/year at Big4 is worse than guaranteed 250k/year that nobody, not even the company's owners can take from you.
That's a worthy idea to learn. I've actually found it quite trivial, which means I'm either too smart or too dumb to understand it. That MDP diagram reminded me of the Feynman's path integral model of electrons: the double slit experiment looks as if electrons take all possible, within constraints, paths and the interference image is the sum of them. Except that in the MDP diagram, parameters of the two slits can vary, within some boundaries, and that varying changes the interference image, so the question that MDP answers is "how the interference image can change if we vary the slits parameters within these boundaries"?
I see classes as nodes in the power grid that transmits and transforms data instead of electricity. These nodes are wired up to other nodes via methods - their binding points. To be precise, a class is more like a spec that can be used to build an instance of that node. In some cases there's only one instance.
The main advantage of classes, I think, is that they define one underlying principle for all these data transformer nodes: that each node has a few binding points with certain interface: named methods. The nodes don't have to look this way, but restricting the freedom of design choices to this pattern makes it easier to compose many nodes together. It's like setting the expectation that all cars are squarish: it's easier to build the infra around cars when you know how they can look in general.
That email will make a senior HR person have a serious talk with 10 other HRs and lawyers, because the matter is non trivial, but their answer will be (delivered by your manager): "you'll get an extra bonus at the next perf cycle." Then they will wait if you settle for this.
For average folks, their ability to deliver is of little importance. What sets their compensation is the market rate. They can slack off for a few years, do bare minimum, then move to another FANG and double their pay, because such is the new market rate. Their past performance means shit. Their ability to perform on interviews and get competing offers means everything.
For exceptional folks it's silly to be the A players unless they have a buddy in the VP ranks who drags them up the ranks, as otherwise they would waste their best years on flat compensation and a bunch of petty bonuses. Exceptional folks should really slack off, become those C players, and build their own gig on a side.
