Related ToolsClaudeClaude CodeChatgptCursorCody

Developers Are Treating AI Like a Calculator, Not a Replacement

AI news: Developers Are Treating AI Like a Calculator, Not a Replacement

Eighteen months into building a serverless Angular and AWS application, one developer's workflow looks nothing like it did a year ago. The progression is one we're hearing constantly now: start with basic AI-assisted search, move to GitHub Copilot, try ChatGPT, then land on Claude for roughly 90% of coding tasks.

The interesting part isn't which tool won. It's how the job itself changed.

This developer describes treating Claude as an "idiot savant" - feeding it detailed specs, screenshots, and structured descriptions to maximize the odds of getting usable output. That's not pair programming. That's project management. The core skill shifted from writing code to writing instructions for something that writes code.

This pattern keeps showing up across developer communities. The developers getting the most out of AI coding tools aren't the ones who type "build me an app." They're the ones who learned to break problems into precise, well-scoped prompts with enough context that the model doesn't hallucinate its way into a disaster. And disasters do happen - this particular developer reports "horrific catastrophes" from both ChatGPT and Claude, which tracks with what we've seen testing these tools ourselves.

The calculator analogy is apt. Nobody accused calculators of replacing mathematicians. They moved the hard part from arithmetic to knowing which equations to run. AI coding assistants are doing the same thing to software development: the hard part is moving from syntax to architecture, from implementation to specification.

That said, the 90/10 Claude-to-ChatGPT split is worth paying attention to. Claude's longer context window (200k tokens, roughly 500 pages of text) and stronger performance on complex code generation tasks have made it the default for developers working on large codebases. ChatGPT still gets used for quick questions and brainstorming, but for sustained coding sessions, Claude has pulled ahead in this segment.

The real question for 2026 isn't whether developers will use AI. It's whether "developer" starts meaning "someone who writes code" or "someone who knows what code to ask for."