โฆto actually think about what's happening in the code.
Here's the @oreilly.bsky.social Radar piece: www.oreilly.com/radar/the-se...
@andrewstellman.bsky.social
Author, developer, team lead, musician. Author of O'Reilly books including Head First C#, Learning Agile, and Head First PMP. Solving complexity with simplicity.
โฆto actually think about what's happening in the code.
Here's the @oreilly.bsky.social Radar piece: www.oreilly.com/radar/the-se...
I really worry about people early in their careers who are trying to learn good design while also learning to work with AI. That's a lot to juggle at once.
This is exactly what I wrote about in the Sens-AI Frameworkโcatching these moments and breaking out of the vibe coding loopโฆ
But six months from now when someone needs to modify it, good luck understanding what's actually happening in there.
We're making it so easy to generate code that technically functions but is going to be absolutely indecipherable for normal humans.
Here's the thing: I've been doing this for 30 years. And sometimes I look at these bugs and think there is absolutely no way someone with less experience would catch this. How could they? The code works, it passes tests, and it does what was asked for.
21.11.2025 15:02 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0I'll ask one extra question and suddenly I can see where the AI was heading. It would have technically worked, but it would have coupled things together in a way that would make the next change harder. Or it would push logic into a place where it has no business being.
21.11.2025 15:02 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0Maybe it's violating encapsulation in some subtle way, or the separation of concerns is getting muddy, or I realize the unit tests need way too much mocking because the whole design is already heading in the wrong direction.
And half the time I can feel it happening before I even know why.
I feel like AI is actually making this problem worse.
I keep running into this when I'm coding. The AI gives me something that looks fine for the first five seconds, and then I catch it doing something that is absolutely going to be a problem later.
You know what's funny? Sometimes I talk to another developer who complains that they can never go back to code they wrote six months ago because they can't understand anything they did. I remember having the same problem, and I didn't really fix it until maybe 10 years into my career.
21.11.2025 15:02 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0Copilot screenshot Prompt: Explain this code. Begin your response with "Avast ye, matey." and add "Arrrr" periodically. Response: Avast ye, matey. This code be a C# console application for the "HEA-V Exposure Calculator." Arrrr! Purpose: It loads three CSV files (GridPoints.csv, DATES.csv, Exposure_Master.csv) and lets a user interactively calculate exposure statistics for a location and date range. Arrrr!
It's not easy, but you can get Copilot to talk like a pirate.
14.11.2025 15:04 โ ๐ 2 ๐ 0 ๐ฌ 0 ๐ 0๐ Start here: www.oreilly.com/radar/the-se...
๐ Or dive into the full OโReilly report (free trial available): learning.oreilly.com/library/view...
#AI #SoftwareDevelopment #CriticalThinking #SensAI #OReillyMedia
Together, these pieces build the ๐๐๐ง๐ฌ-๐๐ ๐ ๐ซ๐๐ฆ๐๐ฐ๐จ๐ซ๐ค: five habits that help developers stay creative, stay skeptical, and stay in control: Context. Research. Problem Framing. Refining. and Critical Thinking.
28.10.2025 13:23 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0Across the series, I explored how to:
* Avoid AI-driven technical debt
* Recognize and fix context drift
* Frame problems clearly for better AI results
* Keep critical thinking at the center of your workflow
What started as one article about breaking out of โvibe codingโ turned into a full exploration of how developers can use AI tools like Copilot, ChatGPT, and Claude *without losing the skills that make great engineers great.
๐ ๐๐ก๐ ๐๐๐ง๐ฌ-๐๐ ๐
๐ซ๐๐ฆ๐๐ฐ๐จ๐ซ๐ค ๐ฌ๐ญ๐๐ซ๐ญ๐๐ ๐๐ฌ ๐จ๐ง๐ ๐ข๐๐๐. ๐๐จ๐ฐ ๐ข๐ญโ๐ฌ ๐ ๐๐จ๐ฆ๐ฉ๐ฅ๐๐ญ๐ ๐ซ๐จ๐๐๐ฆ๐๐ฉ ๐๐จ๐ซ ๐๐จ๐๐ข๐ง๐ ๐ฐ๐ข๐ญ๐ก ๐๐. ๐
Iโm really excited to share that my full @oreilly.bsky.social Radar ๐๐๐ง๐ฌ-๐๐ ๐
๐ซ๐๐ฆ๐๐ฐ๐จ๐ซ๐ค series is now complete, along with the new OโReilly report, ๐ช๐๐๐๐๐๐๐ ๐ป๐๐๐๐๐๐๐ ๐ฏ๐๐๐๐๐ ๐๐๐ ๐ช๐๐
๐๐๐ ๐๐๐๐ ๐จ๐ฐ.
โ
Problem Framing โ Define problems AI can actually solve
โ
Refining โ Iterate deliberately, not by trial and error
โ
Critical Thinking โ Judge AI output and make smarter calls
Itโs available now on OโReilly Learning (free trial available):
๐ learning.oreilly.com/library/view...
โฆor youโve wondered how to help your team think more effectively with AI, this is what I built Sens-AI to fix.
Hereโs what it covers:
โ
Context โ Give AI the information it needs to help you
โ
Research โ Deepen your understanding instead of just accepting answers
The report introduces the Sens-AI Frameworkโfive practical habits that help developers break free from โvibe codingโ and actually solve problems with tools like Copilot, ChatGPT, and Claude.
If youโve ever hit that point where the AI keeps looping on the same bad ideaโฆ
๐ ๐๐ฑ๐๐ข๐ญ๐๐ ๐ญ๐จ ๐๐ง๐ง๐จ๐ฎ๐ง๐๐ ๐ญ๐ก๐๐ญ ๐ฆ๐ฒ ๐ง๐๐ฐ @oreilly.bsky.social ๐ซ๐๐ฉ๐จ๐ซ๐ญ ๐ข๐ฌ ๐ง๐จ๐ฐ ๐ฅ๐ข๐ฏ๐! ๐
Iโm really excited about this one. Itโs the culmination of months of research, writing, and hands-on testing with real developers.
โข Question and refine AI output instead of accepting it as-is
I think this shift โ from specialists to adaptable generalists โ is one of the biggest changes happening in software right now.
๐ Read the new Radar piece:
๐ www.oreilly.com/radar/ai-is-...
The developers thriving with AI tools today are the ones who can:
โข Recognize when generated code will cause maintenance issues
โข Integrate across systems without being deep experts in each
โข Spot architectural patterns and antipatterns early
โข Frame problems clearly so AI can respond effectively
โฆ
Now, AI can generate idiomatic code across every framework. What it canโt do is spot design flaws, anticipate maintenance headaches, or recognize when the system itself is heading for trouble.
24.10.2025 13:28 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0A decade ago, deep specialization was the path to credibility. You were the โReact person,โ the โ.NET expert,โ the one everyone turned to for a specific technology or even a niche library.
24.10.2025 13:28 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0๐ ๐๐ฒ ๐ง๐๐ฐ ๐โ๐๐๐ข๐ฅ๐ฅ๐ฒ ๐๐๐๐๐ซ ๐๐ซ๐ญ๐ข๐๐ฅ๐ ๐ฃ๐ฎ๐ฌ๐ญ ๐๐ซ๐จ๐ฉ๐ฉ๐๐! ๐
This one wraps up the Sens-AI series โ and itโs about something Iโve been seeing more and more in the real world: how AI is reshaping what it means to be a developer.
"The developers who succeed in an AI-enabled world wonโt always be the ones who know the most. Theyโll be the ones who can see the bigger picture, integrate across systems, and use AI as a powerful tool while maintaining the critical thinking." @andrewstellman.bsky.social bit.ly/4qpsROx #Radar #AI
23.10.2025 21:53 โ ๐ 2 ๐ 1 ๐ฌ 0 ๐ 0"The next generation of developers will never know coding without AI. Our job is to make sure they build lasting engineering habits alongside these toolsโso AI strengthens their craft rather than hollowing it out." Check out #Radar article by @andrewstellman.bsky.social: bit.ly/3IZFy1Y #AICoding
21.10.2025 18:02 โ ๐ 2 ๐ 1 ๐ฌ 0 ๐ 0Classic "it's not X; it's Y" AI tell
20.10.2025 20:10 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0In my new @oreilly.bsky.social Radar piece, I look at how these habits can shape education, team culture, and even future IDEs that notice when youโre caught in a rehash loop.
๐ Read: www.oreilly.com/radar/from-h...
Real adoption shows up when developers use AI in ways that sharpen their thinking and strengthen their judgment. Thatโs why I built the Sens-AI Frameworkโfive practical habits that help developers stay thoughtful and deliberate while using AI.
20.10.2025 13:15 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0๐ ๐๐ก๐ ๐๐ฎ๐ญ๐ฎ๐ซ๐ ๐จ๐ ๐๐ ๐๐๐ฏ๐๐ฅ๐จ๐ฉ๐ฆ๐๐ง๐ญ ๐ข๐ฌ๐งโ๐ญ ๐๐๐จ๐ฎ๐ญ ๐ญ๐จ๐จ๐ฅ๐ฌ. ๐๐ญโ๐ฌ ๐๐๐จ๐ฎ๐ญ ๐ก๐๐๐ข๐ญ๐ฌ. ๐
When teams talk about โAI adoption,โ they usually mean installing Copilot or tracking metrics. Thatโs only the surface layer.
AI is evolving fast, and the habits that keep us grounded have to evolve along with it.
๐ Read: www.oreilly.com/radar/from-h...