I'm with you on the avoiding tedium, on-call and monitoring and overall Operations pieces of it.
There's an infrastructure creation aspect where you're creating automation systems and passing it along for others to maintain. I personally think that's a sweet spot.
Everything you said here I relate to, it seemed like you were arguing that infrastructure design and systems engineering is just "app dev ++" as opposed to a collection of skill sets that take years to learn.
It's no different than AI slop if someone thinks cloud automation is just another programming framework to learn. I've worked exactly in 0 companies that got it right when it came to intelligently designed, bullet proof systems. Some of the slop and chaos is so bad it takes big new projects and smarter hires to repair it.
Comments
I'm with you on the avoiding tedium, on-call and monitoring and overall Operations pieces of it.
There's an infrastructure creation aspect where you're creating automation systems and passing it along for others to maintain. I personally think that's a sweet spot.
Everything you said here I relate to, it seemed like you were arguing that infrastructure design and systems engineering is just "app dev ++" as opposed to a collection of skill sets that take years to learn.
It's no different than AI slop if someone thinks cloud automation is just another programming framework to learn. I've worked exactly in 0 companies that got it right when it came to intelligently designed, bullet proof systems. Some of the slop and chaos is so bad it takes big new projects and smarter hires to repair it.