Several times a day, I’m typing in an AI prompt box before my brain has finished formulating the question. It’s of the quickest habits I’ve ever picked up.
Hit a confusing error message, paste it in. See a vague requirement, ask for clarification. Feel a bit stuck, “generate me five options.” Connect it to Jira, hand it your next work ticket, and ask for an implementation plan. None of those is wrong, each reasonable in isolation.
But if you never sit with a problem yourself, you atrophy the mental muscles that are the part of engineering that comes before the answer: the capacity to form a hypothesis before testing it, to feel which option is wrong before you’ve articulated why, to recognize that the actual problem isn’t the one you were asked to solve. None of that comes from prompting. All of it comes from sitting with the problem long enough for your own pattern recognition to fire.
The model is excellent at giving you answers. It’s structurally weaker at the work that happens before the question is well-formed.
So, carve out small protected pockets where you reason without the model. Fifteen minutes on a hard problem, alone, before you ask anyone—model or human—to weigh in. Sketch the shape. Try the wrong answer. Notice what doesn’t fit. Then, if you want, hand it to the model: “Here’s where I got. Critique my reasoning.”
When you bring a half-formed thought to the model, you’re treating it as a collaborator. When you bring a blank prompt, you’re treating it as a script: fill in the blanks, return the output. The second mode produces faster results. The first mode keeps your judgment alive.
You don’t need to do this all day. You need to do it sometimes, deliberately, on the problems that actually matter.