4 ms·
As a mathematician turned software engineer, dev ops and build systems are the bane of my existence. Every time I need to do that work, I want to quit. The fac
by PartiallyTyped 3y ago
As a mathematician turned software engineer, dev ops and build systems are the bane of my existence. Every time I need to do that work, I want to quit.
The fact that I “can’t just X” but need to use some convoluted build system with details hidden somewhere as if it was arcane magic is beyond me.
- hkt 3y agoAlas, lots of devops feel like they're cleverer than they are. I certainly did when I was younger. The sign of seniority in a devops engineer is removing code, breaking down complexity, and being able to design simple, standalone services at a useful level of granularity. Sorry to hear you've not been around those people enough. For what it is worth, even senior devops end up building convoluted crap too, but often this is because the organisation demands it. People don't recognise the hidden costs of complexity, in build or operation. Cleverness is often complexity, and promoting those kinds of solutions means creating the environment for "10x" engineers. People come to rely upon them because investing too deeply in learning about other people's complex legacies is almosy never worth it.
- PartiallyTyped 3y agoAt AWS we are expected to do our own dev-ops, even if you are at a larger project with with some dev-ops engineer, you still need to do your own dev ops for many things. CDK with TypeScript is actually pretty nice to work with, I like the compiler errors, having some type system, and managing my infra via code. My issue is with other systems. In all honesty, our customers have better build tools than we do.