
We started in Part 1 with what the bright shiny What AI (Site builder) Demonstrations Leave out… and it was fairly high level. Now we’re going to dive a bit deeper and yes, somewhat into some technical things. My goal remains: to help level up those in generally more non-technical roles, especially product management. (Though of course, what that technical continuum looks like varies widely.) Let’s start with some basics, and drill down from there…
The dangerous thing about AI coding assistants is that they are often very good.
Huh? How could that be dangerous? It’s dangerous because if they were obviously terrible in spots, we would remain more alert as we used them. Instead, they’re helpful enough to earn trust and inconsistent enough for us to experience times where we clearly shouldn’t have trusted them.
The interaction feels conversational. The agent explains what it is doing, uses reassuring language, and often anticipates the next task. Over time, it becomes easy to stop evaluating each recommendation independently.
That’s the lull.
The assistant is called a copilot for a reason. Do not become its passive passenger.
Disclosure: I did use AI in this series for spelling, grammar and to fill out a few bullet lists with minor items I missed. Generally, I draft, do outlines, and write everything; then have AI check spelling, grammar, and completeness; maybe clean up a few items. Here I did miss some bullets though and those are filled in. Where that was true, I checked sources on ‘truthiness’ for everything. The point is, every high-level thing I go into here are things I’ve personally run into – recently – while working on real projects. So it may seem like a lot, but none of it’s fluff. And you ignore them at some degree of risk.
[Read more…]





