Artificial Intelligence1 min read

Prompting Is Programming

By · Published by Everything Blog

In short

Engineers routinely outperform non-engineers when applying AI to diverse assignments, including travel planning, budgeting, and writing grant proposals. While everyday human conversation naturally relies on shared context to bridge communication gaps, artificial intelligence models merely make plausible guesses when given vague prompts. Unlike non-programmers who might abandon the software or repetitively execute the same query, engineers systematically isolate failing prompt components to debug incorrect outputs.

Key points

  • Effective artificial intelligence prompting requires the same core problem-solving discip…: Effective artificial intelligence prompting requires the same core problem-solving discipline found in traditional computer programming.
  • Software engineers naturally distrust results that merely look correct and routinely acco…: Software engineers naturally distrust results that merely look correct and routinely account for potential edge cases.
  • Troubleshooting flawed artificial intelligence outputs requires systematically adjusting…: Troubleshooting flawed artificial intelligence outputs requires systematically adjusting specific prompt components rather than repeating identical instructions.

Sources checked by our analysis pipeline: 1

The other day I watched a friend of mine, an Ivy League-educated professor in the liberal arts, work with Claude. The conversation went in circles, and they never articulated what their goal was. Each reply from Claude was reasonable given what it had been told, and each one was a little off from what my friend actually wanted, so they’d nudge it, and it would drift somewhere else. This is one of the smartest people I know, and I was watching them struggle with a tool that has completely reshaped the way I build software.

That interaction came to mind when I was reading about how industries outside of software aren’t seeing productivity gains from AI. Marketers, analysts, managers, and operations folks get some help drafting emails and summarizing meetings, then spend the time they saved cleaning up plausible-looking output that doesn’t quite do what they needed. The org-wide productivity gains that were promised mostly haven’t materialized. For software engineers, the change is night and day. I basically stopped writing code within a few weeks of Opus 4.5 shipping, and…

Artificial Intelligence