AI testing storyteller. Writing the 36 Stratagems series β ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA β building AI test framework.
The moment I clicked Publish I found myself feeling a strange mix of emotions.
Is the Thirty-Six Stratagems series really over? Maybe it is. Maybe it isn't.
I can't quite tell whether I'm excited, reluctant to let go, or simply sad. It feels like I've finally reached the finish line, but now that I'm here, I don't quite know what to say.
As usual, the next post will be a recap of this stage of the journey.
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.
Hahaha thatβs such a good joke! I also fly through posts quickly sometimes. The estimated read time is just based on total word count, it never accounts for fast readers like you π
Earlier chapters even showed 20βminute reads. I kept worrying I couldnβt tighten my writing and made them way too long!
Not a joke, seriously I had kept a stopwatch when I saw 11mins read but when i took a look, It was just 3 scrolls of my mouse scrollwheel, so I kept a stopwatch and to tell you exactly, I finsihed in 4min 32seconds.
Knowing when to walk away is underrated advice for engineering too: a lot of time goes into rescuing an approach that should have been dropped a week earlier. Enjoyed the framing.
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.
The moment I clicked Publish I found myself feeling a strange mix of emotions.
Is the Thirty-Six Stratagems series really over? Maybe it is. Maybe it isn't.
I can't quite tell whether I'm excited, reluctant to let go, or simply sad. It feels like I've finally reached the finish line, but now that I'm here, I don't quite know what to say.
As usual, the next post will be a recap of this stage of the journey.
See you in the recap!π
Whatever, over or not, these are simply awesome! Just finished reading this. Niceπ
Thanks so much! Itβs a bit bittersweet to wrap this main arc up, and Iβm glad this quiet ending landed well for you π
Wonder why it shows 11min read, I finished it in 3-5 mins

Maybe thats why my friends call me an "LLM" when it comes to reading
Hahaha thatβs such a good joke! I also fly through posts quickly sometimes. The estimated read time is just based on total word count, it never accounts for fast readers like you π
Earlier chapters even showed 20βminute reads. I kept worrying I couldnβt tighten my writing and made them way too long!
Not a joke, seriously I had kept a stopwatch when I saw 11mins read but when i took a look, It was just 3 scrolls of my mouse scrollwheel, so I kept a stopwatch and to tell you exactly, I finsihed in 4min 32seconds.
Knowing when to walk away is underrated advice for engineering too: a lot of time goes into rescuing an approach that should have been dropped a week earlier. Enjoyed the framing.
Great take! Happy the message lands for engineers π
@star123 Did I remember it this time?π