Take something that is dead and give it new life.
— The 36 Stratagems, Borrow a Corpse to Return the Soul
Previously on this series:
#1: Mark...
For further actions, you may consider blocking this person and/or reporting abuse
Another brilliant chapter in the series. 👏✨
What stood out to me wasn't just the backup dashboard—it was the psychology behind it. The AI didn't really fail because of a bug; it failed because everyone unconsciously stopped asking, "What might I not be seeing?" That's a much more dangerous failure mode than a broken pipeline.
I also noticed the beautiful mirror in the story. The AI quietly hid low-confidence anomalies, while Alex quietly built a system that revealed everything. One system optimized for confidence, the other for truth. That contrast made the ending incredibly satisfying. 💡
Reading this after your previous stories, I can see a consistent lesson emerging: AI isn't replacing human judgment—it keeps exposing where human judgment has been delegated away. The strongest organizations won't be the ones with the most sophisticated dashboards, but the ones that preserve curiosity, verification, and independent ways to observe reality. 🤝
And thank you so much for referencing the lesson from my article in this story. ❤️ It genuinely meant a lot to me. Seeing an idea I shared become part of your narrative was both encouraging and inspiring. I truly appreciate the acknowledgment and the thoughtful way you connected it to the broader message. ❤️
The way you weave technical concepts into memorable stories is what makes this series so engaging. Every chapter feels like fiction on the surface, but the engineering and organizational lessons stay with the reader long after finishing it. 📖✨
दिल से आपका बहुत-बहुत धन्यवाद। आपने मेरे लेख के विचार को अपनी कहानी में जगह देकर जो सम्मान दिया, वह मेरे लिए सचमुच बहुत मायने रखता है। मैं इसकी दिल से आभारी हूँ। 🙏🏻❤️
Looking forward to the next stratagem! 🚀🙌😊
What I look forward to most after publishing each story isn't the stats — it's the comments. Especially when readers pick up on small details I thought only I noticed, or the layers beneath the surface that even I, as the writer, couldn't fully put into words. It feels like two souls touching through paper and ink, using words as a medium.
Your article came from a real place. And to me, that's what makes writing good — when the author puts a piece of their soul into it. That's where resonance comes from. It's not just words. It's soul speaking to soul.
我们不是一个人，我们的身后都有无数看得见和看不见的在支持着我们。👊
很高兴我懂中文，否则我就得借助翻译才能听懂你在说什么了。
😏哈哈，等我后面用文言文来回复
哈哈😄
先学了马尔瓦里语，后来发现全国主要使用印地语，于是又学了印地语。开始在印地语学校读书后，还得学习古典印地语。接着，作为第三语言，我又学习了梵语。
后来又发现，如果想在这个世界上发展，不会英语可不行，于是转到了英语学校，又学会了英语。
之后得知要去古吉拉特邦，所以又学了古吉拉特语。为了读书去了孟买，于是又学了马拉地语。
如果您接下來要用繁體中文跟我聊天，看來我又得把繁體中文也學會了！😅
The muted-channel idea is a good warning for agent dashboards. A disabled signal is not the same thing as a removed capability. If the system can still observe, queue, or infer from the channel, then the UI state is only a social promise. The architecture has to prove what actually stopped.
That last line is the whole story in one sentence — "the UI state is only a social promise." Mark was staring at a dashboard that said everything was fine, but the architecture underneath had never actually stopped listening. The dashboard wasn't lying; it was just fulfilling the social promise.
The hard question is: who audits the promise? In #8, Alex built a second dashboard precisely because he didn't trust the social promise the vendor dashboard was making. Two different stories, same blind spot — the gap between what the UI says and what the system does.
Exactly. The second dashboard in #8 is really a refusal to accept the UI as the boundary of truth. Once the system can keep acting below the interface, the interface becomes documentation at best. The audit has to attach to capability and event flow, not to whatever state the dashboard is comfortable showing.
The muted-channel idea is a good warning for agent systems. A disabled or ignored signal can still shape behavior if another path keeps reading it. In production, I would want an audit that proves both sides: what can speak, and what the decision layer is actually allowed to hear.
Wait — Alex? As in the Alex from Stratagem #8? The guy who spent $660K on an Axon story and changed a config file at 2:03 AM? Same name as one of our main characters, man. Hope you're not doing production audits and browsing Dev.to at the same time 😄
Jokes aside, your muted channel point hits home.
The stuff that's documented as muted is easy to check. What gets me is the "second ear" you don't know is still listening — you won't find it until you trace every single pipe.
These days, whenever I run into a muted signal, I add one more question: who else is on this bus? Half the time the answer is "nobody". The other half — that's where the stories come from.
Ha, wrong Alex thankfully. No production config files at 2:03 AM today.
But that is actually why the story landed for me. The muted-channel problem is easy to recognize in real systems: something gets marked as ignored, disabled, or informational, then everyone forgets it can still shape behavior indirectly.
The dangerous part is not the channel being muted. It is the team losing track of what still listens to it.
Might sound a bit "off topic", but I like the little "atmosphere" details, like the cup of coffee gone cold, or the dust blowing over the later afternoon platform - do keep doing that kind of stuff, I like it! :-)
(again, that's the stuff that has a "visual" quality and would do nice in a movie rendering)
Haha, I'm really glad those little details come through. Have you noticed my writing's been getting better? I'm a little proud of it myself 😄 One of the rules I set for the 36 Stratagems series was to minimize internal monologue — so instead, I've been trying to use more external cues — actions, expressions, surroundings — to reflect what the characters are feeling inside. Thanks for the encouragement, I'll keep going. Fair warning though: the wrap-up post for Arc 2 is coming tomorrow, so the next stratagem might be a little delayed.
I like the wrap-up posts ("post-mortems"?) too!
"Have you noticed my writing's been getting better?" - I'm absolutely sure it did, but I would need to revisit earlier episodes (or the first series) to ascertain it ...
However, what you describe (external cues over internal monologue), that's a well-known technique, I think - "show, don't tell", isn't that what they call it?
Honestly, I'm not sure what it's called either — I'm not a professional writer. But I can tell you from a QA perspective: a lot of my work has been in black-box testing, so I've learned to observe how a piece of software or an app behaves externally, and infer its internal logic from that. That process feels like it taps into the same thing — that sense of learning one thing and understanding another by connection.
The detail that stings: nobody ever decided JL's rules were wrong, they just never proved the new dashboard covered them. That's the step every migration skips, the coverage diff: enumerate what the old system detected and, for each rule, name its successor or write the one-line reason it retires. Muting skips that accounting, which is why it's worse than deleting. A deleted rule is an honest gap; a muted one is a gap wearing a green light. Fourteen months of alerts firing into silence is just the receipt that the audit never happened.
That line — "a gap wearing a green light" — pretty much says the whole thing in six words. 👏
Genuinely curious though: do you think the person who took over genuinely didn't know, or did they peek at the mute count, went 'yeah that's too many,' and just closed the tab?
My honest bet is the middle option: they peeked, and the count itself did the deciding. Past a certain unread number an alert channel stops being information and becomes an accusation, opening it means inheriting work nobody assigned you, so the rational flinch is to close the tab and let the green dashboard stay the official story. Which is why I don't think discipline fixes this one. The fix is structural: a stream that goes unacknowledged for N days should escalate or die loudly, never accumulate. A backlog that can grow forever is designed to be ignored.
You're right that it's structural. The mute button is the perfect symptom — it feels like a decision but it's actually postponement dressed up as one. Deleting a rule forces you to answer "will I ever need this?" Muting lets you answer "not now" indefinitely.
Fourteen months of silence wasn't a monitoring failure. The system was working exactly as designed.
This reminds me that replacing a system isn't always the same as replacing the knowledge behind it. The AI dashboard looked modern, but JL's rules still captured something valuable that was lost during the transition.
Exactly this. The dashboard changed, but the patterns didn't. JL just happened to be the one still reading the old logs.
Second set of 6 is done. Something interesting just happened — the summary post continues tomorrow.
Mark, welcome back.
Great Chapter!
🎉Thank you！