Over the past weeks, I’ve been sharing a series of posts that gravitate around one question:
How do we use AI without outsourcing our judgment?
T...
For further actions, you may consider blocking this person and/or reporting abuse
That line about confusing productivity with removing friction is the one I'd underline. A lot of the friction AI takes away is exactly where the understanding used to get built, so "faster" and "learned less" end up being the same motion. Naming that gap honestly is worth more than any single tool for closing it.
I agree Nazar. It took several discussions to reach that exact framing. I am glad that it resonates.
The "Am I using AI intentionally?" loop has the single-party authorship problem at the core. The engineer doing the cognitive work is the same one assessing whether the cognition was real or outsourced. That's the cognition evaluating itself, which is the structure that gets you into comprehension debt in the first place. A self-administered Thinking Balance Tracker has the same blind spot as a self-reported time log. The version of yourself that filled it out is the one whose calibration you were trying to check.
The discriminator that breaks out of that: external test of understanding. Pair-explain to someone who didn't write the code. Blind code-review without AI assistance, scheduled and unannounced. A second engineer who asks "why this decision" and gets an answer the author has to defend live. Anything that puts the assessment outside the loop being assessed.
Where the Toolkit lands cleanly: the team-edition heatmap, because comprehension is being mapped by people other than the original implementer. That's the version of these tools that has structural bite. The individual self-tracking versions are useful for noticing, less useful for measuring.
Very true. Some tools are more indicators to increase awareness. Others are more for measuring.
Exactly, and the failure mode is reading an indicator as a measurement. An awareness tool's job is to make you go look. A measurement's job is to tell you what you found. Those are different epistemics, not two ends of one dial. The moment a self-tracker's number gets quoted as if it were measured, you've borrowed authority the tool was never built to issue, which is the single-party problem one level up. Keep the indicators honest about being indicators and the toolkit holds. Congrats on the launch.
That is an important distinction to make. I have tried to specify this across my resources. Thanks for highlighting this point!
the 'cognitive offloading' framing is the right one for why this resonates. it's not that AI is bad at producing output, it's that the productive friction of building something yourself is where judgment gets calibrated.
the engineers who lose the most aren't the ones who use AI too little. they're the ones who stop noticing when they've stopped thinking. the output looks right. the understanding isn't there. you only find out three weeks later when the system breaks in a way you can't debug because you never understood the decision that built it.
a toolkit that addresses that specifically is worth paying attention to. the question I keep coming back to: what's the minimum friction that still preserves judgment? what can be offloaded safely versus what always needs the human in the loop?
Well said Mudassir. Those are the tradeoffs I am trying to find balance with.
Thank you for this @javz! I really love that you are offering your knowledge to the DEV community especially since many software engineers today suffer from over reliance on AI whether it is intentional or not. Keep doing what you are doing!
Thanks for the kind words and support Elmar!!
I am an AI Engineer and Full Stack Developer based in Japan with 8 years of professional software development experience. Throughout my career, I have built scalable web applications, AI-powered solutions, cloud-based systems, and end-to-end digital products for various industries.
My expertise spans both frontend and backend development, as well as modern AI technologies, including machine learning, large language models (LLMs), automation, and intelligent application development. I enjoy turning complex ideas into practical, high-quality products that deliver real business value.
I am currently interested in collaborating with professionals, startups, and companies across North America and Europe. I value long-term partnerships, knowledge sharing, and opportunities to work on innovative projects with global teams.
Working internationally allows me to combine my technical expertise, Japanese market experience, and passion for emerging technologies to help build impactful products for a worldwide audience.
If you're looking for a reliable AI Engineer and Full Stack Developer to collaborate on exciting projects, I'd be happy to connect and explore opportunities together.
Congratulations on the launch! 💗 This is far more than just another developer resource—it's a reminder that the real value of an engineer isn't measured by how quickly they can write code, but by how effectively they think, analyze, and solve problems.
In today's AI-driven world, generating code has become easier than ever, but critical thinking, system design, decision-making, and engineering judgment remain the true differentiators. Tools can accelerate development, but they can't replace curiosity, experience, or the ability to ask the right questions.
I really appreciate the effort you've put into creating something that encourages developers to strengthen these fundamentals. Resources like this help the community grow beyond syntax and frameworks, focusing instead on mindset and long-term engineering excellence.
Thank you for sharing your knowledge with the Dev Community. Wishing you tremendous success with the Thinking Engineer Toolkit—I hope it reaches thousands of developers and inspires them to become not just better coders, but better engineers. Keep building and keep inspiring! 👏🔥
I am so glad this resonates with you! And thank you so much for your support!!
nice man
thanks Ben :)
no problem:)
Amazing stuff and what the industry needs right now. It addresses the real risk of cognitive offloading in AI workflow. Thank you for sharing it.
Thanks for the support Natasha! It means a lot :)
Impressive work!
thanks leob!
Congratulations!
Thanks!