Unsure what you mean here. Do you mean because teams can only have so many heads at certain levels, the people who are holding those seats block others from getting promoted?
754 karma · joined January 4, 2019
Unsure what you mean here. Do you mean because teams can only have so many heads at certain levels, the people who are holding those seats block others from getting promoted?
Much more performant and naturally relational way of generating data than looping recursively.
Ie. you don't want to hire dev A because it took them just 2 weeks to figure out how to deploy a change to Prod instead of 4.
How do you actually do that though?
Employees typically have incentive to perform their own function to the best of their abilities. This manifests as things like compliance theatre, excessive/impractical IT policies, over-engineering the software, features/products built for the sake of it.
There is so much accidental complexity cruft and ceremony involved with the writing of unit tests and making things unit testable. In a lot of cases, the "coverage" is an illusion and the tests add more friction than there really ought to be.
There's a tier that sits in the middle who write "platform" software on top of "systems" but for "applications", but you could argue that those people are much closer to app devs than system software devs so they may as well be lumped in with them.
There is simply less supply of systems jobs and they have a higher talent requirement, so it's pretty rational for people to be content to stay at the application dev layer.
Where is the evidence that systems devs get paid more? My impression is that lots of systems development historically has been unpaid or paid via open source foundations. And the route to getting paid doing that kind of work seems a lot more bumpy and less straight forward, almost like a "starving artist" kind of life story.
Whereas app dev is pretty simple. You go to college, you crank on LeetCode for a couple of weeks and then you get a 6 figure salary working on JIRA tickets. It's a brainless, hard to get wrong life script.
Your primary residence should be thought of as a consumption item, whether you rent or own. If homes cost more to buy or rent since the QE (and they do) then we absolutely have had consumer price inflation.
How could the majority of people collect a salary working on software that has no users? That makes no sense.
My impression is that the primary purpose of Kubernetes is to give SRE teams political air cover to rewrite a lot of their existing processes. Whether Kubernetes is actually required for that, or even net superior seems questionable. This unsexy work becomes justifiable because it's coupled to a mainstream accepted tech modernization.
You see this same phenomenon with database migrations. Where what the team really needed to do is just rewrite an app to use the existing database properly. But no one is going to approve that work. So what happens is people convince themselves that the existing tech sucks and use that to rationalize doing the rewrite. The result ends up not always being net superior, because sure you did the rewrite but you are also eating the operational cost of integrating a new technology into the org.
Can you elaborate? What exactly about Kubernetes improved the developers life?
That doesn't sound very liquid to me.
It's not always in one's control to avoid complexity. The simplest solution to a problem in a lot of cases may be 2-3x the lift (simplicity tends to require more work, complexity is easy) and thus blocked by the business. A holistically simpler solution may be blocked politically because a certain team doesn't want to own some functionality etc ...
I would say the best developers can see complexity coming and have a healthy fear of it, the medium devs don't mind complexity and the worst devs can't get anything done without increasing complexity.
This seems like a false dichotomy. Avoiding obvious performance mistakes such as the ones you mentioned does not require additional focus that would detract from general building. It just requires that you know what you are doing.
If you are the type of person who makes said mistakes, its unlikely you would ever go back and fix them by "focusing" on performance because the issue is simply that you don't know what you don't know. Likely someone else will come along in future and point out your mistakes to you.
Optimization that actually hinders you from building and requires focus is at the very margins and almost no one is going to those levels in typical "application" code.
This feels like a strawman. I have yet to see an instance of this in my 10 years. The much, much, much more common case is people justifying half-assed shoddy work with YAGNI.
When you constantly apply this "only things bigger than X matter" reasoning you still end up with slow, shitty software but you just died by a thousand cuts instead of 1.
This. There's a lot of very very smart people who are totally lost among the trees on the technicalities of Bitcoin who don't get this 1 simple aspect. It's never happening.
I think for some people though, this might be an acceptable trade off (even temporarily) where they favor being able to WFH and not need to be tethered to train lines / highways for commuting over being "close to the action".
If companies offered this trade off across the board it would be a good way to retain employees over the long term as your life situation changes (kids etc ...) you can kind still find a place at the same company that can accomodate the lifestyle you desire at that point in time.
A decent workaround is to have entirely remote teams and entirely in-office teams. That way people can be on teams where they feel like being remote is not a detriment to their careers (because ALL discussion takes place online) and people who prefer working in-person don't have to force everything onto Slack just to have the remote people feel included.