3 ms·
That pretty much describes my "career" of the past 20 years. Lately it's been getting harder and harder to get _any_ job. These days it's either web dev which h
by capr 3y ago
That pretty much describes my "career" of the past 20 years. Lately it's been getting harder and harder to get _any_ job. These days it's either web dev which has reached unbearable levels of idiocracy with its endless tail-chasing web frameworks, microservices and even the platform itself (DOM/CSS), or it's million-line C++ legacy-on-arrival abstraction shitfests written by OOP-heads. It feels like there's nowhere to run.
- conor- 3y agoI've found that "devops" is a pretty nice niche to fall into, even with all of its warts. And that means devops as in literally a developer who can also provision/manage infra and operations and not just a YAML jockey who gets a buzzword title. You can kind of pick your lane: dev-experience tooling, build systems, infrastructure automation, observability systems, etc. It's a nice way to break out of the rat race of bad practices and questionable frameworks being used all over the place and it seems pretty secure because most of the tail-chasing framework types aren't exactly keen to learn the details of what actually takes code from 0 to production-grade so having the breadth of knowledge becomes an asset that lets you work on a variety of problems. Obviously there's a different slew of annoying things to deal with (wrangling cloud services, insane abstraction around infrastructure, etc.) but I think those are more pleasant to work around. The infra-side of things also hasn't really slowed down in hiring like pure developer positions has.
- capr 3y agoThat could work except there's just as much BS in devops as in dev. The fact that this job title exists at all to me is a symptom of the same problem.