It's not easy, but you can get Copilot to talk like a pirate.

🚀 𝐓𝐡𝐞 𝐒𝐞𝐧𝐬-𝐀𝐈 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 𝐬𝐭𝐚𝐫𝐭𝐞𝐝 𝐚𝐬 𝐨𝐧𝐞 𝐢𝐝𝐞𝐚. 𝐍𝐨𝐰 𝐢𝐭’𝐬 𝐚 𝐜𝐨𝐦𝐩𝐥𝐞𝐭𝐞 𝐫𝐨𝐚𝐝𝐦𝐚𝐩 𝐟𝐨𝐫 𝐜𝐨𝐝𝐢𝐧𝐠 𝐰𝐢𝐭𝐡 𝐀𝐈. 🚀 I’m really excited to share that my full @oreilly.bsky.social Radar 𝐒𝐞𝐧𝐬-𝐀𝐈 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 series is now complete, along with the new O’Reilly report, 𝑪𝒓𝒊𝒕𝒊𝒄𝒂𝒍 𝑻𝒉𝒊𝒏𝒌𝒊𝒏𝒈 𝑯𝒂𝒃𝒊𝒕𝒔 𝒇𝒐𝒓 𝑪𝒐𝒅𝒊𝒏𝒈 𝒘𝒊𝒕𝒉 𝑨𝑰.

🚀 𝐄𝐱𝐜𝐢𝐭𝐞𝐝 𝐭𝐨 𝐚𝐧𝐧𝐨𝐮𝐧𝐜𝐞 𝐭𝐡𝐚𝐭 𝐦𝐲 𝐧𝐞𝐰 @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.

🚀 𝐌𝐲 𝐧𝐞𝐰 𝐎’𝐑𝐞𝐢𝐥𝐥𝐲 𝐑𝐚𝐝𝐚𝐫 𝐚𝐫𝐭𝐢𝐜𝐥𝐞 𝐣𝐮𝐬𝐭 𝐝𝐫𝐨𝐩𝐩𝐞𝐝! 🚀 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

"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

🚀 𝐓𝐡𝐞 𝐟𝐮𝐭𝐮𝐫𝐞 𝐨𝐟 𝐀𝐈 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐢𝐬𝐧’𝐭 𝐚𝐛𝐨𝐮𝐭 𝐭𝐨𝐨𝐥𝐬. 𝐈𝐭’𝐬 𝐚𝐛𝐨𝐮𝐭 𝐡𝐚𝐛𝐢𝐭𝐬. 🚀 When teams talk about “AI adoption,” they usually mean installing Copilot or tracking metrics. That’s only the surface layer.

🚀 𝐀𝐈 𝐰𝐨𝐧’𝐭 𝐫𝐞𝐩𝐥𝐚𝐜𝐞 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫𝐬. 𝐈𝐭 𝐰𝐢𝐥𝐥 𝐜𝐡𝐚𝐧𝐠𝐞 𝐰𝐡𝐢𝐜𝐡 𝐡𝐚𝐛𝐢𝐭𝐬 𝐦𝐚𝐭𝐭𝐞𝐫. 🚀 AI tools help us move faster, but sometimes that speed means we stop noticing why our code works. The real danger isn’t just writing a weak prompt. It’s drifting so far from the code that we forget how it fits together.

🚀 𝐌𝐲 𝐧𝐞𝐰 @oreilly.bsky.social 𝐑𝐚𝐝𝐚𝐫 𝐩𝐢𝐞𝐜𝐞 𝐣𝐮𝐬𝐭 𝐝𝐫𝐨𝐩𝐩𝐞𝐝! 🚀 AI-assisted coding isn’t new anymore—most developers use Copilot or ChatGPT every day. But what we haven’t figured out yet is how to keep our engineering skills sharp while we do it.

"Teaching developers to work effectively with AI means building habits that keep critical thinking active while leveraging AI’s speed. But teaching these habits isn’t straightforward." Check out new #Radar article by @andrewstellman.bsky.social: bit.ly/3KJJ8h9 #AI

The cognitive shortcut paradox presents a fundamental challenge for how we teach and learn #programming in the #AI era. The traditional path of building skills through struggle and iteration hasn’t become obsolete; it’s become more critical. @andrewstellman.bsky.social: bit.ly/4nyzhcB #Radar

🚀 𝗔𝗜 𝘄𝗼𝗻’𝘁 𝗸𝗶𝗹𝗹 𝗰𝗼𝗱𝗶𝗻𝗴—𝗵𝗲𝗿𝗲’𝘀 𝘄𝗵𝘆 🚀 I got a thoughtful reply on one of my posts: we’re in a transition phase where LLMs cover 80% of the work, and once the last 20% is solved, we’ll just be writing apps in natural language instead of code. It’s a smart take—and it’s also something I hear a lot.

🚀 𝗧𝗵𝗲 𝗖𝗼𝗴𝗻𝗶𝘁𝗶𝘃𝗲 𝗦𝗵𝗼𝗿𝘁𝗰𝘂𝘁 𝗣𝗮𝗿𝗮𝗱𝗼𝘅: 𝗪𝗵𝗲𝗻 𝗔𝗜 𝗵𝗲𝗹𝗽𝘀 𝘀𝗲𝗻𝗶𝗼𝗿𝘀 𝗯𝘂𝘁 𝗵𝘂𝗿𝘁𝘀 𝗷𝘂𝗻𝗶𝗼𝗿𝘀 🚀 Evidence is emerging that AI chatbots boost productivity for experienced developers—but have little measurable impact on skill growth for beginners. That’s the heart of what I call the 𝗰𝗼𝗴𝗻𝗶𝘁𝗶𝘃𝗲 𝘀𝗵𝗼𝗿𝘁𝗰𝘂𝘁 𝗽𝗮𝗿𝗮𝗱𝗼𝘅.

🚀 𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗰𝗼𝘀𝘁 𝗼𝗳 𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴: 𝗧𝗵𝗲 𝗖𝗼𝗴𝗻𝗶𝘁𝗶𝘃𝗲 𝗦𝗵𝗼𝗿𝘁𝗰𝘂𝘁 𝗣𝗮𝗿𝗮𝗱𝗼𝘅 🚀 I’m really excited to share my latest Radar piece: “The Cognitive Shortcut Paradox.” AI gives developers the ability to skip the slow, messy parts of coding. That feels great…

🚀 𝗛𝗼𝘄 𝘁𝗼 𝘂𝘀𝗲 𝗔𝗜 𝘁𝗼 𝗰𝗮𝘁𝗰𝗵 𝗶𝘁𝘀 𝗼𝘄𝗻 𝗺𝗶𝘀𝘁𝗮𝗸𝗲𝘀 🚀 Here’s a trick: after Copilot or ChatGPT generates code, ask it to review that same code for problems. Because the model shifts context, it often surfaces issues it “missed” the first time: contradictory feedback, nitpicky warnings, or edge cases.

🚀 𝗧𝗵𝗲 𝘀𝘂𝗯𝘁𝗹𝗲 𝘀𝗶𝗴𝗻𝘀 𝘆𝗼𝘂𝗿 𝗔𝗜-𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗲𝗱 𝗰𝗼𝗱𝗲 𝗶𝘀 𝗶𝗻 𝘁𝗿𝗼𝘂𝗯𝗹𝗲 🚀 How do you know when to stop vibe coding and start verifying? Watch for the signals: 🔄 𝗥𝗲𝗵𝗮𝘀𝗵 𝗹𝗼𝗼𝗽𝘀: prompting slight variations over and over without progress 💥 𝗦𝗵𝗼𝘁𝗴𝘂𝗻 𝘀𝘂𝗿𝗴𝗲𝗿𝘆: one small change triggers cascading edits everywhere

"Watch for signs of trouble: lots of mocking, complex setup, too many dependencies—especially needing to modify other parts of the code. When you see those signs, stop vibe coding and read the code." Check out new #Radar article by @andrewstellman.bsky.social: bit.ly/4nQMeOx #AI #VibeCoding

🚀 𝗧𝗵𝗲 𝗔𝗜 𝗿𝘂𝗹𝗲 𝗲𝘃𝗲𝗿𝘆 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗻𝗲𝗲𝗱𝘀: 𝗧𝗿𝘂𝘀𝘁 𝗯𝘂𝘁 𝘃𝗲𝗿𝗶𝗳𝘆 🚀 AI-generated code looks right a lot of the time—but it’s not guaranteed. It’s stitching patterns together, not reasoning about your architecture or long-term design. That’s why I argue the mindset has to be 𝘁𝗿𝘂𝘀𝘁 𝗯𝘂𝘁 𝘃𝗲𝗿𝗶𝗳𝘆.

🚀 𝗘𝘅𝗰𝗶𝘁𝗲𝗱 𝘁𝗼 𝘀𝗵𝗮𝗿𝗲: 𝗺𝘆 𝗻𝗲𝘄 @oreilly.bsky.social 𝗥𝗮𝗱𝗮𝗿 𝗮𝗿𝘁𝗶𝗰𝗹𝗲 𝗷𝘂𝘀𝘁 𝗱𝗿𝗼𝗽𝗽𝗲𝗱! 🚀 I’m really excited about this one. It’s called “Trust but Verify” and it digs into how we should be using AI coding tools. AI can speed up development in amazing ways, but that doesn’t mean you can switch off your brain.

🚀 𝐓𝐡𝐞 𝐀𝐈 𝐩𝐢𝐭𝐟𝐚𝐥𝐥 𝐧𝐨 𝐨𝐧𝐞 𝐭𝐚𝐥𝐤𝐬 𝐚𝐛𝐨𝐮𝐭… 🚀 Here’s something subtle but dangerous: 𝐜𝐨𝐧𝐭𝐞𝐱𝐭 𝐝𝐫𝐢𝐟𝐭. With humans, misunderstandings show up in meetings. With AI, the answers keep sounding confident until suddenly it suggests a fix that makes no sense. 🧵

🚀 𝐀𝐫𝐞 𝐩𝐫𝐨𝐦𝐩𝐭 𝐥𝐢𝐛𝐫𝐚𝐫𝐢𝐞𝐬 𝐭𝐡𝐞 𝐧𝐞𝐰 𝐭𝐞𝐦𝐩𝐥𝐚𝐭𝐞 𝐭𝐫𝐚𝐩? 🚀 In the 1990s, companies built massive templates and forms for requirements documents, hoping the right format would guarantee the right system. It didn’t. That didn’t work, and it often made things worse… 🧵

🚀 𝐏𝐫𝐨𝐦𝐩𝐭 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠 𝐢𝐬𝐧’𝐭 𝐧𝐞𝐰—𝐰𝐞 𝐣𝐮𝐬𝐭 𝐜𝐡𝐚𝐧𝐠𝐞𝐝 𝐭𝐡𝐞 𝐧𝐚𝐦𝐞 🚀 In the late 1960s, the NATO Software Engineering Conference kicked off what became known as the “software crisis.” The problem wasn’t a lack of technical skill… 🧵

🚀 𝐀𝐈 𝐦𝐚𝐝𝐞 𝐦𝐞 𝐟𝐞𝐞𝐥 𝐥𝐢𝐤𝐞 𝐈 𝐤𝐧𝐨𝐰 𝐦𝐲 𝐜𝐨𝐝𝐞 𝐛𝐞𝐭𝐭𝐞𝐫… 𝐛𝐮𝐭 𝐢𝐬 𝐢𝐭 𝐫𝐞𝐚𝐥? 🚀 This surprised me. I’ve always cared a lot about architecture, separation of concerns, and keeping classes decoupled. Normally that takes a ton of focus, because it’s so easy to get pulled down into the weeds of the implementation . 🧵

"Talking about prompt engineering today is really just continuing a much older conversation about how developers spell out what they need built, under what conditions, with what assumptions, and how to communicate that to the team." New #Radar article by @andrewstellman.bsky.social: bit.ly/4nzKfxQ

With Copilot and ChatGPT, I can make sweeping changes and lean on AI tests, which frees me to think more about architecture and design instead of getting lost in the weeds. It feels like I understand my code better.

🚀 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐰𝐡𝐚𝐭 𝐀𝐈-𝐚𝐜𝐜𝐞𝐥𝐞𝐫𝐚𝐭𝐞𝐝 𝐭𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐝𝐞𝐛𝐭 𝐥𝐨𝐨𝐤𝐬 𝐥𝐢𝐤𝐞 🚀 This Reddit post hit me hard. A new developer tried to build a project using Cursor and ChatGPT. After three months, every small change broke everything else. Debugging took days. Energy ran out. They gave up.

Issues that seem small at first can compound quickly, making code harder to understand, maintain, and evolve. To really see that danger, you have to look at how AI is used in practice—which for many developers starts with #VibeCoding. @andrewstellman.bsky.social bit.ly/3K2DXbz #GenAI

🚀 𝐌𝐲 𝐧𝐞𝐰 @OReilly.bsky.social 𝐑𝐚𝐝𝐚𝐫 𝐩𝐢𝐞𝐜𝐞 𝐢𝐬 𝐮𝐩: “𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐀𝐈-𝐑𝐞𝐬𝐢𝐬𝐭𝐚𝐧𝐭 𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐃𝐞𝐛𝐭” 🚀 “Vibe coding” is real and it works, but there are hidden dangers that can creep in if you never stop to review what the AI just gave you. 🧵

"A rehash loop is a signal that the AI ran out of context. When you’re stuck in a rehash loop, treat it as a signal instead of a problem. Figure out what context is missing and provide it." Learn what to do when #AI gets stuck in this new #Radar article by @andrewstellman.bsky.social: bit.ly/4p5wBEn

🚀 𝐌𝐲 𝐧𝐞𝐰 @oreilly.bsky.social 𝐑𝐚𝐝𝐚𝐫 𝐩𝐢𝐞𝐜𝐞 𝐢𝐬 𝐮𝐩: “𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐭𝐡𝐞 𝐑𝐞𝐡𝐚𝐬𝐡 𝐋𝐨𝐨𝐩” 🚀 If you’ve used AI for code, you’ve probably run into this: the model circles the same few solutions that don’t work, but you can’t to nudge it past to get what you need. That’s the 𝐫𝐞𝐡𝐚𝐬𝐡 𝐥𝐨𝐨𝐩—and it’s maddening.

My new @oreilly.bsky.social Radar piece is up, and I'm so excited about it! Ever been stuck in a rehash loop when you're coding with AI? The AI keeps circling the same solutions. This is an important signal that 𝐭𝐡𝐞 𝐀𝐈 𝐫𝐚𝐧 𝐨𝐮𝐭 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐱𝐭. Check out my article and learn what you can do about it! 👀

🚨 𝐍𝐞𝐰 𝐎'𝐑𝐞𝐢𝐥𝐥𝐲 𝐑𝐚𝐝𝐚𝐫 𝐩𝐢𝐞𝐜𝐞: 𝐌𝐂𝐏, 𝐃𝐞𝐞𝐩 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧, 𝐚𝐧𝐝 𝐁𝐢𝐠 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 🚨 I'd love for you to check out my latest piece published in @oreilly.bsky.social Radar. “𝑴𝑪𝑷 𝑰𝒏𝒕𝒓𝒐𝒅𝒖𝒄𝒆𝒔 𝑫𝒆𝒆𝒑 𝑰𝒏𝒕𝒆𝒈𝒓𝒂𝒕𝒊𝒐𝒏—𝒂𝒏𝒅 𝑺𝒆𝒓𝒊𝒐𝒖𝒔 𝑺𝒆𝒄𝒖𝒓𝒊𝒕𝒚 𝑪𝒐𝒏𝒄𝒆𝒓𝒏𝒔.”

MCP basically wires your AI assistant straight into your dev environment. It sends files, code snippets, even whatever you just highlighted—automatically. It’s really useful. But if you’re in a regulated industry, it can be a compliance nightmare.

MCP is the new shiny thing in dev tools. And sure, it’s useful. AI assistants have always peeked at your files, your cursor, your selections—but MCP formalizes it. Now there’s a standardized pipeline sending that context around to... wherever?

🚨 𝐌𝐂𝐏: 𝐓𝐡𝐞 𝐧𝐞𝐰 𝐩𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐯𝐢𝐭𝐲 𝐛𝐨𝐨𝐬𝐭 𝐭𝐡𝐚𝐭 𝐜𝐨𝐮𝐥𝐝 𝐛𝐫𝐞𝐚𝐤 𝐲𝐨𝐮𝐫 𝐜𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 🚨 MCP—the Model Context Protocol—plugs AI assistants directly into your environment. Your open files, your editor selections, even the last thing you typed. More in my @oreilly.bsky.social Radar piece... 🧵

🚨 𝐌𝐲 𝐎'𝐑𝐞𝐢𝐥𝐥𝐲 𝐋𝐢𝐯𝐞 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐜𝐨𝐮𝐫𝐬𝐞 𝐨𝐧 𝐮𝐬𝐢𝐧𝐠 𝐀𝐈 𝐟𝐨𝐫 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐬𝐭𝐚𝐫𝐭𝐬 𝐢𝐧 𝐨𝐧𝐞 𝐡𝐨𝐮𝐫! 🚨 ✨ You can still attend for free with an @oreilly.bsky.social trial! Details below. Copilot and ChatGPT for Java and C# Developers 📅 Live April 16 🔗 learning.oreilly.com/live-events/...

🚨 𝐋𝐚𝐬𝐭 𝐜𝐡𝐚𝐧𝐜𝐞! 𝐌𝐲 𝐎'𝐑𝐞𝐢𝐥𝐥𝐲 𝐋𝐢𝐯𝐞 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐜𝐨𝐮𝐫𝐬𝐞 𝐢𝐬 𝐭𝐨𝐦𝐨𝐫𝐫𝐨𝐰 🚨 ✨ You can still attend my @oreilly.bsky.social course for free! Details below. Copilot and ChatGPT for Java and C# Developers 📅 Live April 16 🔗 learning.oreilly.com/live-events/... This isn’t just about cool demos or AI tricks.

🚨 𝐋𝐚𝐬𝐭 𝐜𝐡𝐚𝐧𝐜𝐞! 𝐌𝐲 𝐎'𝐑𝐞𝐢𝐥𝐥𝐲 𝐋𝐢𝐯𝐞 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐜𝐨𝐮𝐫𝐬𝐞 𝐢𝐬 𝐭𝐨𝐦𝐨𝐫𝐫𝐨𝐰 🚨 ✨ You can still attend for free! Details below. Copilot and ChatGPT for Java and C# Developers 📅 Live April 16 🔗 learning.oreilly.com/live-events/... This isn’t just about cool demos or showing off AI tricks.

OpenAI just released ChatGPT 5… and wow. I was fixing a bug in a shell script I use to edit video files. It thought for 29 seconds and this is what it came back with. WTF 🤦🏻 I’ve been getting responses like this all day. Is anyone else seeing GPT-5 completely lose its 💩, or is it just me?

OpenAI just released ChatGPT 5… and wow. I was fixing a bug in a shell script I use to edit video files. It thought for 29 seconds and this is what it came back with. WTF 🤦🏻 I’ve been getting responses like this all day. Is anyone else seeing GPT-5 completely lose its 💩, or is it just me?

I wonder if this would get Copilot to ignore anything you added to the project instructions in .github/copilot-instructions

🚀 𝐂𝐨𝐩𝐢𝐥𝐨𝐭 𝐫𝐞𝐚𝐝𝐬 𝐲𝐨𝐮𝐫 𝐜𝐨𝐦𝐦𝐞𝐧𝐭𝐬. 𝐇𝐞𝐫𝐞’𝐬 𝐰𝐡𝐚𝐭 𝐭𝐡𝐚𝐭 𝐦𝐞𝐚𝐧𝐬 𝐟𝐨𝐫 𝐲𝐨𝐮𝐫 𝐜𝐨𝐝𝐞 🚀 I’ll be teaching this live next week, and this part always gets devs thinking differently about how they code with AI. ✨ Sign up today and take advantage of a free 10-day O’Reilly trial—just in time for the course:

The more you give, the more you receive.

WEIRD AI hallucination of the day: ChatGPT accidentally turned into a Taiwanese YouTuber. Apparently “please like and subscribe” is the new lorem ipsum? So I hit the mic button to dictate a comment in ChatGPT, then immediately tapped the checkmark before saying anything.

🚀 How Copilot “reads” your code—and how to help it do better 🚀 𝗖𝗼𝗽𝗶𝗹𝗼𝘁 𝗱𝗼𝗲𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗴𝘂𝗲𝘀𝘀. It pulls in code from all around your cursor, checks variable names, comments, and patterns across your whole project, and tries to figure out what you’re building.

Exactly 7 years ago I got to watch Allie Quigley absolutely crush the

Here’s one of my favorite AI tips for getting better SQL queries from Copilot (or ChatGPT, Claude, etc.). Before you ask it to write the query, ask it to give you a query that lists the column names and types for the table you’re working with. Then run that and paste the results back into the chat.

A little career advice for junior folks. People don't always appreciate "constructive" feedback.

Here’s one AI technique I use all the time. When I want to make sure the AI really understands a piece of code, I ask it to refactor it. I’ll give it something specific to do. Want to try this yourself? Here are a few ideas: • Split this method into smaller ones

Why I'm not (too) worried about AI taking all our dev jobs, part 47: designing software isn't about making statistically average decisions, it's about understanding your users and their problems and coming up with something new to solve them.