4 ms·
I don't disagree on any of your points. I just have to point out that part of the reason we're having this argument is the dual treadmill of title inflation and
by GauntletWizard 4y ago
I don't disagree on any of your points. I just have to point out that part of the reason we're having this argument is the dual treadmill of title inflation and bad practices insisting they're best practices. SRE will not be the title for much longer, and DevOps was a bad title from the beginning and a flash in the pan but it was the title from 2010-2015.
- dijit 4y ago> I just have to point out that part of the reason we're having this argument is the dual treadmill of title inflation and bad practices insisting they're best practices. Yeah, that's a really good point. > SRE will not be the title for much longer, and DevOps was a bad title from the beginning and a flash in the pan but it was the title from 2010-2015. I hope the terms become better defined, not less, though. What do you think the next title will be.
- GauntletWizard 4y agoIf I knew, I'd have already put it on my LinkedIn. I see "Automation Engineer" around a bit, but I don't think that's quite right. "Cloud Architect" is already taken by a specific kind of title inflation (and a few actually great software engineers who absolutely deserve it). My best guess is around "Orchestration" - "Orchestration Engineer", "Cloud Orchestrator", maybe even "Orchestration Technician" if the vogue becomes "Humility".