oh my piece is up! so "ops/infra teams" used to be redundant, but now we have infrastructure engineers (who do no operations) and operations engineers (who do no infrastructure). what does this divergence mean for your career and mine? I HAZ THOUGHTS https://acloudguru.com/blog/engineering/the-future-of-ops-jobs

among those thoughts:

* unless you are an infra company, your mission is not doing infrastructure. which means "infrastructure is technical debt" (the original topic of this essay)

* the underlying technological changes are both forcing devs to level up at ops skills to survive (microservices, the death of autoinstrumentation) and democratizing access to operational information (observability, the abstracting away of infrastructure)

* operability has become both far more challenging and far more important than ever. ops skills are _desperately_ needed.

* but the old niche of "run infra for non-infra companies" is slowly withering away as those companies get better options.