3 ms·
This resonates. Trying to get back into a tech job and they all need Kubernetes experience because microservices. I've spent 10 years developing MVPs that never
by marcus_holmes 2y ago
This resonates. Trying to get back into a tech job and they all need Kubernetes experience because microservices. I've spent 10 years developing MVPs that never scaled past 100 users, let alone anywhere large enough to need K8s.
- fxtentacle 2y agoYou'll fit in just fine. Most of the companies that want Kubernetes also never scaled past 100 users ;)
- nejsjsjsbsb 2y agoAnd the ones that did have a platform team, you just write code as if you are using a lambda or something anyway. Tend to your allotment of in-house yaml and off to the races! Unless you want to be on the k8s team. I wouldn't hate it personally.
- Cthulhu_ 2y agoSame, at this point it feels like doing your own k8s configuration is re-solving an already solved problem. Surely deploying software in a scalable fashion is a solved problem?
- nejsjsjsbsb 2y agoFor most AWS etc. can solve it for you. At a certain scale that gets expensive enough to make reinventing wheels attractive.
- mittermayr 2y agoIt's a fifty/fifty, isn't it, part of it is actually exciting. Everytime I have a foot in a "proper" company (usually for a consulting gig), I'm always excited to learn about a bunch of stuff that I never had a moment to work with (because, as you say, it's usually a waste of time when there's less than a 100k users on it). The other part, however, is the insane slowdown of progress this usually brings with it. Everything, is, so, incred-ibly-slow at these corps. And policy and asking for permission and nobody wanting to be responsible unless upper management and and and...
- adamc 2y agoBureaucracy is real. There are often ways of surmounting that, but that takes yet another, different set of skills.