I find models vastly more useful than most technical books in my own work because I know how to feed in the right context and then ask them the right questions about it.
There isn't a book on earth that could answer the question "which remaining parts of my codebase still use the .permission_allowed() method and what edge-cases do they have that would prevent them from being upgraded to the new .allowed() mechanism"?
No one really cares how you found all those .permission_allowed() calls to replace - was it grep, or intense staring, or AI model. All that matters is you stand behind it, and act as an author. Original post said it very well:
> ChatGPT isn’t on the team. It won’t be in the post-mortem when things break. It won’t get paged at 2 AM. It doesn’t understand the specific constraints, tech debt, or your business context. It doesn’t have skin in the game. You do.
You're so close to realising why the book counter argument doesn't make any sense!
Those people exist and they’re wrong.
More frequently, however, I find I’m judging the model less than its user. If I get an email that smells of AI, I ignore it. That’s partly because I have the luxury to do so. It’s largely because engaging has commonly proven fruitless.
You see a similar effect on HN. Plenty of people use AI to think through problems. But the comments that quote it directly are almost always trash.
Because the output is almost always trash, and it takes re-doing the work and then claiming that it came from LLMs for it not to be.
These tools are being sold to me as similar to what a Jr engineer offers me, but that's not at all true because I would fire a Jr that came to me with such bullshit and needing such significant hand-holding so often as what I see coming out of an LLM.