150 karma · joined March 2, 2022
There’s a lot to unpack in that sentence, which is to say there’s a lot of complexity it removes.
Agree it does add as well.
I’m not convinced k8s is a net increase in complexity after everything is accounted for. Authentication, authorization, availability, monitoring, logging, deployment tooling, auto scaling, abstracting the underlying infrastructure, etc…
What alternative behavior do you suggest?
OIDC seems to be the de-facto standard today.
https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
Maybe you can help them make or save even more.
The written design defends against, “this is just a toy” even if you’ve thought it through for countless hours.
How would a developer build an iOS app without using any system calls or OS frameworks? Xcode?
“Infrastructure” is a blurry concept in such a deeply integrated system.
Today it still works.
Edit: OK, there is such a thing. I guess this is why I never played the truenamer class. Point still stands.
The risk with this type of developer is they often prioritize their toolset and amazing code over the actual businesses needs. I’ve seen it lead to the wrong tool being used for the job.
A couple years later when these devs move on the business has a harder time maintaining the code they leave behind.
There are always drifters to be hired, which has some value.