But Nothing Has Changed on Our Side: A Reflection on Stagnation
I argue that despite the relentless pace of technological advancement and external market shifts, our internal processes and fundamental approaches remain stubbornly unchanged. This article explores the uncomfortable reality that while the world evolves, our organization has failed to adapt, creating a dangerous gap between potential and performance that threatens our future relevance.
The most dangerous illusion we face is believing that because the world changes around us, we have somehow changed with it.
- Terretta
Refreshingly written. And like wading into the ocean on a surprisingly hot spring day, bracing.
At most any given scope, "most" systems you interact with aren't under your own control. For this, consider: because that's true, the fault is yours for not grappling with that reality.
This has been written about before:
But even that was missing a bullet:
- recognize that my code will interact with systems I cannot anticipate, that change in ways I cannot control, and become coupled more than ever intended
- preetham_rangu
Nothing changed on our side" and "it's DNS" are the same sentence. Both mean "I haven't looked yet
- rufo
I have a history of asking incredibly basic questions about the assumptions that are going in to a debugging issue for exactly these kinds of reasons. Something changed somewhere; so have we verified our basic assumptions that things are what we think they are... or did something change under our feet without our knowing? Or maybe we actually have a different understanding of the state of the world, and one of us is actually wrong?
It's not fruitful every time, but the number of times you skip asking those questions and chase something around, only to realize that, actually, it _was_ the ridiculous/simple thing... well, it feels a lot better to realize it earlier :)
(personal footnote: do be mindful of the context you're asking in! I feel like in general those sorts of questions are _fairly_ well tolerated by technical people. Sometimes you feel a bit stupid asking the question, but many of the systems I've worked on are large and complicated enough that it's not that weird - and if there's downtime and a healthy team, people genuinely want to hunt every possibility down. People not used to that, though, will sometimes bristle a bit, thinking you're implying that they're stupid and don't understand the basics. There can be ways to be more tactful, but at the very least, it's worth being aware of that reaction so you can follow up with a "just making sure I understand!" or something like that.)