The detail I’d put above everything else is on the procedure sheet, before the test starts. The 120-second window and the end conditions were approved in advance and identical for both runs, so when the group package doesn’t form, the record reads INCOMPLETE_IN_WINDOW rather than FAILED, and Leo doesn’t rerun it.
That’s what I keep getting wrong. I’ve had two identical deployments a day apart, immediate on one and forty seconds on the other, and I only worked out my window afterwards. Agreeing it beforehand, with a witness on the sheet, is what makes the second run evidence rather than an anecdote.
And the hashes are an escalation now. #33: a hash says whether the file changed, not whether it was right. #34: the manifest arrives inside the package it describes. #35: the list can be changed too, and it doesn’t prove the events happened. Each one defeats the last one’s instrument.
Also, a Long Black and a Flat White, nobody having ordered. That café has a better memory than most monitoring systems. Interesting!!😄
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
That's a thoughtful observation. I especially like your point about agreeing on the time window before the test begins.🎉
There's an important distinction between an incomplete result and a failed result. Once we define the rules after seeing the outcome, we're no longer testing against a standard. We're adjusting the standard to fit the evidence.
And your connection between #33, #34, and #35 is exactly the progression I wanted to explore. Every new layer of verification eventually exposes another weakness in the previous one.👍
As for those two coffees... perhaps the man has been keeping his own records all along. He just doesn't need a monitoring dashboard to remember who came in. 😄
And there's just one more stratagem left. It should be coming in the next few days. Haha!🤣
Thank you for this lovely series. As always, I'm excited to read and curious to know what the final stratagems will be, but I am not ready for the end of this series.😀
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
JavaScript enthusiast with a growing passion for Python. I love exploring the world of programming, experimenting with code, and discovering new ways to turn ideas into reality.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Hahaha, congrats on grabbing the third spot! 🎉 That's right, we're finally down to the last one. Thank you for sticking with me all the way from the beginning of the series to the final chapter. Let's wait and see what the last one brings. It might be coming sooner than you think. Hahaha!😄
Honestly love how you connect ancient military tactics to modern QA and system meltdowns—the 35th stratagem hits way too close to real production bugs 😄 Great series!
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Hmmmm Lena and Leo the Dynamic Duo doing something deviously clever here which we can't yet fully discern - have they set a trap, or what? On to the Grand Finale ... !
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Hahaha, only one stratagem left! I’ll push hard to finish it. Hard as it is to let go, it’s time to wrap things up — though maybe it won’t quite end yet, who knows 😂
You mean "cliffhanger", and maybe "all will not yet be revealed", at least not fully? Kinda makes sense, because that would otherwise require a pretty gargantuan number of threads to be 'tied up' ... but, let's not get ahead of ourselves!
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Exactly! I’ve actually settled on the ending long ago. Many things don’t need a full explanation; blank spaces leave room for imagination. Now I partly understand the pain of long‑form novel writers, hahaha 😂
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
I am a freelance Data Scientist with a proven record of delivering high‑impact, data‑driven solutions that strengthen strategy, security, and innovation.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
6th Comment here👋
The detail I’d put above everything else is on the procedure sheet, before the test starts. The 120-second window and the end conditions were approved in advance and identical for both runs, so when the group package doesn’t form, the record reads INCOMPLETE_IN_WINDOW rather than FAILED, and Leo doesn’t rerun it.
That’s what I keep getting wrong. I’ve had two identical deployments a day apart, immediate on one and forty seconds on the other, and I only worked out my window afterwards. Agreeing it beforehand, with a witness on the sheet, is what makes the second run evidence rather than an anecdote.
And the hashes are an escalation now. #33: a hash says whether the file changed, not whether it was right. #34: the manifest arrives inside the package it describes. #35: the list can be changed too, and it doesn’t prove the events happened. Each one defeats the last one’s instrument.
Also, a Long Black and a Flat White, nobody having ordered. That café has a better memory than most monitoring systems. Interesting!!😄
That's a thoughtful observation. I especially like your point about agreeing on the time window before the test begins.🎉
There's an important distinction between an incomplete result and a failed result. Once we define the rules after seeing the outcome, we're no longer testing against a standard. We're adjusting the standard to fit the evidence.
And your connection between #33, #34, and #35 is exactly the progression I wanted to explore. Every new layer of verification eventually exposes another weakness in the previous one.👍
As for those two coffees... perhaps the man has been keeping his own records all along. He just doesn't need a monitoring dashboard to remember who came in. 😄
And there's just one more stratagem left. It should be coming in the next few days. Haha!🤣
Thanks for following the series so closely!😆
Thank you for this lovely series. As always, I'm excited to read and curious to know what the final stratagems will be, but I am not ready for the end of this series.😀
Thanks a lot! I also feel reluctant to wrap it up, but the final stratagem is coming soon 😂
First reaction, first comment! 🥇
🎉🎉🎉Hahaha, thanks for your support! Congrats, you’re the first one!😆
🥳
👏That was so fast! Impressive!
2nd 🥰
Hahaha, here comes the second place! Congratulations and thanks for your support!🎉
Here I come, the 3rd supporter! We're at #35 now, just one more to go. I have a feeling the last one is going to be a banger 😃
Hahaha, congrats on grabbing the third spot! 🎉 That's right, we're finally down to the last one. Thank you for sticking with me all the way from the beginning of the series to the final chapter. Let's wait and see what the last one brings. It might be coming sooner than you think. Hahaha!😄
Honestly love how you connect ancient military tactics to modern QA and system meltdowns—the 35th stratagem hits way too close to real production bugs 😄 Great series!
Thank you so much! It means a lot that the tactics feel grounded in real production pain. Only one stratagem left!😆
Welcome!
哇 😀 老哥好久不见,今天这篇文章 可真长
大结局马上了,稍微收不住笔,哈哈哈
真期待最后一章🤩
这段时间工作太忙了 都没时间上dev了 每天醒来然后就上学 上学完后就工作
😰
很充实,就差恋爱了
唉🙂
Hmmmm Lena and Leo the Dynamic Duo doing something deviously clever here which we can't yet fully discern - have they set a trap, or what? On to the Grand Finale ... !
Hahaha, only one stratagem left! I’ll push hard to finish it. Hard as it is to let go, it’s time to wrap things up — though maybe it won’t quite end yet, who knows 😂
You mean "cliffhanger", and maybe "all will not yet be revealed", at least not fully? Kinda makes sense, because that would otherwise require a pretty gargantuan number of threads to be 'tied up' ... but, let's not get ahead of ourselves!
Exactly! I’ve actually settled on the ending long ago. Many things don’t need a full explanation; blank spaces leave room for imagination. Now I partly understand the pain of long‑form novel writers, hahaha 😂
I like it!😊
😆Thankyou like it!
nice job boss
😆Hahaha, well said! I’ve notified HR — you’re getting a promotion and a raise soon 🎉