Prompting Still Matters
Something I have been noticing lately concerns me, and I think it is worth a closer look.
The Pattern
As LLMs have become significantly better at reasoning, the quality of our inputs to them seems to be getting worse. There is an inverse relationship forming: the more capable the model, the less effort some of us are putting into prompting it.
Think back to when we first moved away from auto-complete tools and started prompting our early GPT models. We were deliberate and intentional. We explained the context, described what the code was doing, and were precise about what we wanted to change. Nobody serious would have typed “fix this code” and called it a day.
That discipline appears to be slipping.
The Real Cost
Some might reason: “Why should I think hard about the problem when the model can do it for me?” But that thinking has a direct financial consequence.
Frontier models are expensive. When we reach for the most powerful reasoning model available – not because the task demands it, but because it compensates for a vague or underspecified prompt – the company pays twice:
- Our salary, for reasoning we are not doing
- Token costs, for the compute required to overcome our weak input
Those costs are real and they accumulate.
The Deeper Risk
More concerning than the cost is what this habit does to us as knowledge workers. Our ability to analyze, reason, and articulate problems clearly is the core of what we do. If we are systematically outsourcing that to a model, that capability atrophies. And if our reasoning ability is no longer adding value – because a model is doing it instead – then we have undermined our own professional case.
The developers who should genuinely fear AI displacement are not those who use AI well. They are those who allow AI to replace the thinking they should be doing themselves.
The Skill We Should Keep Sharp
Using a smaller, cheaper model effectively because you have invested effort in a well-structured, precise prompt is a mark of skill. It demonstrates that you understand the problem, and it is better for the team and the business.
Let’s stay sharp. Match the model to the task and invest in the quality of your prompts.