"Kubernetes is not developer-friendly". I couldn't agree more here.

Having worked at a few startups ranging from 50-500 people I notice a push for full stack developers to own all of this. I remember an outburst of this developer who found out in addition to having to learn yet another JS framework they also had to learn docker, k8 and become an expert in AWS by the end of the week. So that begs the question, where is the line? Of course if you work at a startup of 5 people, you're in charge of everything but I can see as companies push for leaner engineering teams, the title "Full Stack Developer" becoming literally a one dev army.

Learning and being bad at k8 makes me ask what does it mean to be a "good" developer anymore? If I took a dev who was an expert at creating good abstractions and making O(n) code and told them they had to learn 2 new JS frameworks and a container orchestration tool and be able to deploy and manage that in the cloud is that too much? Would it be enough for that person to be O.K. at making abstractions, and ships O(n2) code every once in a while but they know how to use k8 and manage the stack on AWS?

To your point about platform teams abstracting complexities out for developers; while I agree that's the point of having a good engineering enablement team, I would argue that not all shops abstract the same way. Wouldn't it be better to just learn k8s straight up so as a dev you'd be more employable? One of the things that worries me about having a platform team abstract this away is that companies will demand that developers "know k8" and may not find "I used k8 but through this custom in-house tool" a proper response.

Software Engineer | Product Leader