3 ms·
The author and I share nearly identical work histories. I've been in IT for about 10 years, starting with AWS and database administration, then turned more DevO
by sudofail 8y ago
The author and I share nearly identical work histories. I've been in IT for about 10 years, starting with AWS and database administration, then turned more DevOps with a focus on CI/CD. Over the last few years, it's become very obvious that the DevOps role is requiring more and more development skills. Simple bash scripting is not going to cut it in the modern tech company.
A couple years ago I made the switch to full time development. I now do most of the DevOps stuff for my teams, but from a developer role, instead of a sysadmin/cloudops role.
I'm certain that's going to be the future. Look at Google's requirements for SREs. They are full-fledged software engineers.
- ragona 8y agoI’ve gotten to a point where if we write a bash script for something I consider it somewhat of a failure. I want operational tooling to be easily maintainable by a large team of software engineers, and bash scripts just aren’t that. Services that run services is the way to go. Lose a box from the fleet? No problem, the operator service bounced it and got it running again. I’ll admit that timelines often mean you don’t get to build the grand vision out of the gate, but I absolutely agree with you that bash scripting isn’t how we should be running services these days.