The model is fast, fluent and sure, and that is the problem

I use models daily now. For reading a wall of unfamiliar logs, drafting a migration script, or explaining a config format I have not touched in years, they save me real hours.

Where they fail is exactly where my job lives: causes. Ask why a site is slow and you get a confident, well-structured list of plausible reasons, in the tone of someone who has looked. Nothing has looked. It is the most convincing guess in the room, and guessing is the thing I have spent nine years training myself not to do.

So I split the work. Anything where being wrong is cheap and obvious, the model does. Anything where being wrong means telling a client the wrong story, I do, with the logs open.

The interesting part is what this does to junior developers. The output looks like the work of someone experienced, which makes it much harder to notice you have not understood anything yet.