This article didn’t resonate with me as much as I was expecting.
While the insights on developer influencers was sharp, the article itself felt like more of a reaction than an evaluation.
I’ve worked in many legacy companies. The rationale for staying on the tech stack they have, and the approach they take to DevOps, is not particularly well reasoned. Often they are experiencing painful consequences due to their adherence to old design patterns.
I wanted each paragraph to be more diagnostic, frankly more reminiscent of the wide ranging and interesting debate we find here (especially when the old guard shows up and speaks with real authority and wisdom on how the problems they solve don’t map to Kubernetes, etc.).
I’d really welcome counter-arguments to the point I’m making, so I’ll frame it this way:
This felt like the same kind of “playing to the crowd” that dev influencers do, just a different crowd.
I think the point that should be well taken is that if you're hoping to service the greater programming community, you can't do so in your ivory tower solutions on a community Ill equipped to utilize them. From experience, DevOps done poorly is terrible and demoralizing. Agile done poorly (often) is terrible and slow. Take any best practice and try to apply it to any organization and you'll get a lot of flaming wreckage. Ideally those companies will have some pragmatic people that can nudge their people in the right direction gradually.
While the insights on developer influencers was sharp, the article itself felt like more of a reaction than an evaluation.
I’ve worked in many legacy companies. The rationale for staying on the tech stack they have, and the approach they take to DevOps, is not particularly well reasoned. Often they are experiencing painful consequences due to their adherence to old design patterns.
I wanted each paragraph to be more diagnostic, frankly more reminiscent of the wide ranging and interesting debate we find here (especially when the old guard shows up and speaks with real authority and wisdom on how the problems they solve don’t map to Kubernetes, etc.).
I’d really welcome counter-arguments to the point I’m making, so I’ll frame it this way:
This felt like the same kind of “playing to the crowd” that dev influencers do, just a different crowd.