3 ms·
Thank goodness there a people that get this. I ran screaming from a devops role I'd been in for two years around 6 months ago. This thought process of "complexi
by nineteen999 9y ago
Thank goodness there a people that get this. I ran screaming from a devops role I'd been in for two years around 6 months ago. This thought process of "complexity == good", "old == bad" - watching the company starting to pull apart an already unstable product and break it down into microservices when they could't even document their existing codebase, how to bootstrap a new instance.
Most puppet installations I've seen run by these small teams just degenerate into snowflake factories. Going to all that effort to run a huge packer pipeline so your templates are the same accross all your clouds providers - and then pulling whatever-the-current-random-version-of-a-bunch-of gems from rubygems.org onto hundreds of different machines. Arggggh!
The argument I keep hearing is that "if we don't use all the latest tools then how are we going to attract the best talent".
Every few years I dip my toes back into the devops space, just to see if it's improving. Nope. It's just getting worse.