Much of what is said here about agile could equally be said of devops, a term that's been drained of whatever blood was pumping through it to the point that it functionally doesn't mean anything anymore.
Conversation
Notices
-
Embed this notice
mhoye (mhoye@mastodon.social)'s status on Saturday, 20-Apr-2024 23:22:43 JST mhoye -
Embed this notice
mhoye (mhoye@mastodon.social)'s status on Saturday, 20-Apr-2024 23:22:42 JST mhoye I mean, somehow we went got from A to B here and it's reasonable to ask what the hell happened.
I suspect very strongly that the real answer is that we're seeing the scattered, burning rubble of a scorched-earth epistemological and semiotic warzone here, where process burden after process burden are being thrown in the path of those who seek understanding and nearly intimacy by people whose whole id and purpose depend on the ongoing primacy of command-and-control as the operational zeitgeist
-
Embed this notice
mhoye (mhoye@mastodon.social)'s status on Tuesday, 23-Apr-2024 00:04:00 JST mhoye I'm not sure what's complicated about it, the diagram is very clear.
-
Embed this notice
Eaton (eaton@phire.place)'s status on Tuesday, 23-Apr-2024 00:04:00 JST Eaton @mhoye oh, come ON, that’s obviously a portrait of Gannon
-
Embed this notice
Andy Nortrup :cascadia: 🌳 (andy@social.seattle.wa.us)'s status on Tuesday, 23-Apr-2024 00:04:01 JST Andy Nortrup :cascadia: 🌳 @mhoye the first rule of agile these days is to not talk about agile. Just slowly built better, shorter feedback loops anywhere you can.
-
Embed this notice
Cat Hicks (grimalkina@mastodon.social)'s status on Tuesday, 23-Apr-2024 00:04:01 JST Cat Hicks @andy @mhoye I'm really curious what a "feedback loop" is. Really really specifically. Because feedback is a million different things and I see this phrase used a lot. This is a real question not a provocation like what does feedback loop mean to you?
-
Embed this notice
mhoye (mhoye@mastodon.social)'s status on Tuesday, 23-Apr-2024 00:04:02 JST mhoye The same general shape of thing happened to DevOps.
The core insight of DevOps was that if you have to carry the pager for the code you're writing, you'll make better software. It was, if in some near trivial way, an way to shackle the quality of a developer's life directly to the failure cases of their software.
In retrospect, it was clear that idea would not be allowed to live.
So what we call DevOps today - functionally "vendor contract micromanagement via CLI" - is not that at all.
-
Embed this notice
mhoye (mhoye@mastodon.social)'s status on Tuesday, 23-Apr-2024 00:04:02 JST mhoye In both cases, it's worth thinking about where the original Agile and DevOps philosophies _position_ their adherents. Because in both cases, that position can be fairly described as "as close as possible to the consequences of, and people affected by, decisions made about software".
And in the same vein I think it's worth asking ourselves who, specifically, are well-served by debasing and diluting those ideas, by distancing people and pushing responsibility and agency away from consequence.
-
Embed this notice