4 ms·

Sounds like they want a devops person and not a developer. I understand the line is often blurred. I think it comes down to if the role is deploying K8’s etc. o

Sounds like they want a devops person and not a developer. I understand the line is often blurred. I think it comes down to if the role is deploying K8’s etc. or just using it. If they are administering it then I’d hope that they would be able to answer those questions. Good teams contain a balance of skills and abilities. It’s not unreasonable to want someone stronger in some areas than others to compliment the team. A diversity of talents also helps so that people teach each other.

treeman79 5y ago
Seen some companies fail because everyone was expected to be full devops in addition to core speciality. Almost no one could get anything useful done. Mostly because kub was simply to much of a time sink.
- hackerfromthefu 5y ago
  Honestly find this hilarious, and a sign of the low experience levels prevalent across the industry, with inflated titles etc. What should happen in these situations, is someone with enough experience should be able to say this isn't working as well as previous ways, and guide to more sensible practices that suit that companies situation. This is very hard when 'everyone is a senior' and 'i read this blogpost lets cargo cult it'.. The older crafts industries had masters, journeymen, and apprentices, in a more hierarchical structure, and while more rigid led to much less of the kind of massive waste of effort your post talks about where 'Almost no one could get anything useful done' .. which you've seen at multiple companies!
neurotrace 5y ago
Absolutely. I recently dropped in to a job where I was led to believe I'd be spending most of my time architecting applications but I've spent most of my time on ops stuff. Every engineer is expected to have more than a working knowledge of AWS, Terraform, and Kubernetes. I don't know how anyone gets anything done
- hn_version_0023 5y ago
  > I don't know how anyone gets anything done Does work actually get done? Genuinely curious. I don’t think that many experts could reasonably come to consensus on much of anything!

treeman79 5y ago

Seen some companies fail because everyone was expected to be full devops in addition to core speciality. Almost no one could get anything useful done. Mostly because kub was simply to much of a time sink.

hackerfromthefu 5y ago
Honestly find this hilarious, and a sign of the low experience levels prevalent across the industry, with inflated titles etc. What should happen in these situations, is someone with enough experience should be able to say this isn't working as well as previous ways, and guide to more sensible practices that suit that companies situation. This is very hard when 'everyone is a senior' and 'i read this blogpost lets cargo cult it'.. The older crafts industries had masters, journeymen, and apprentices, in a more hierarchical structure, and while more rigid led to much less of the kind of massive waste of effort your post talks about where 'Almost no one could get anything useful done' .. which you've seen at multiple companies!

neurotrace 5y ago

Absolutely. I recently dropped in to a job where I was led to believe I'd be spending most of my time architecting applications but I've spent most of my time on ops stuff. Every engineer is expected to have more than a working knowledge of AWS, Terraform, and Kubernetes. I don't know how anyone gets anything done

hn_version_0023 5y ago
> I don't know how anyone gets anything done Does work actually get done? Genuinely curious. I don’t think that many experts could reasonably come to consensus on much of anything!