logoalt Hacker News

Writing code is cheap now

205 pointsby swolpersyesterday at 5:20 PM267 commentsview on HN

Comments

alexjrayyesterday at 6:08 PM

"Writing" code is cheap but this just scratches the surface. Its a completely different paradigm. All forms of digital generation is cheap and on the verge of being fully automated which comes with self recursion loops.

Automated intelligence is now cheap....

light_hue_1today at 9:47 AM

Writing code was always cheap! You could outsource for inconsequential amounts of money and get massive amounts of code in return. Yet, the vast majority of companies do not do so. Because coding is not the hard part of being a software engineer / programmer.

That's like saying that photography killed painting because it saved you from having to draw things. Drawing is basically free now, I just take the photo. But the number of painters (and by that I mean, artists who paint) is dramatically higher today than in 1800. Artists didn't die because of mechanical reproduction, they flourished, because that wasn't the problem they were solving.

snowhaleyesterday at 6:04 PM

the interesting shift is where the time goes. before: thinking + typing. now: thinking + reviewing. the thinking part didn't get cheaper -- domain knowledge, edge cases, integration constraints -- none of that is free. what changed is you now review AI output instead of type your own, which is genuinely faster but not as different as it sounds. the hard part was always understanding what to build, not the keystrokes.

show 1 reply
submetatoday at 8:24 AM

I think the framing is still too code-centric.

The real bottleneck isn’t writing (or even reviewing) code anymore. It’s:

1. extracting knowledge from domain experts

2. building a coherent mental model of the domain

3. making product decisions under ambiguity / tradeoffs

4. turning that into clear, testable requirements and steering the loop as reality pushes back

The workflow is shifting to:

Understand domain => Draft PRD/spec (LLM helps) => Prompt agent to implement => Evaluate against intent + constraints => Refine (requirements + tests + code) => Repeat

The “typing” part used to dominate the cost structure, so we optimized around it (architecture upfront, DRY everywhere, extreme caution). Now the expensive part is clarity of intent and orchestrating the iteration: deciding what to build next, what to cut, what to validate, what to trust, and where to add guardrails (tests, invariants, observability).

If your requirements are fuzzy, the agent will happily generate 5k lines of very confident nonsense. If your domain model + constraints are crisp, results can be shockingly good.

So the scarce skill isn’t “can you write good code?” It’s “can you interrogate reality well enough to produce a precise model—and then continuously steer the agent against that model?”

mentalgearyesterday at 6:03 PM

Sometimes it feels what we are seeing is Code becoming just like any other "asset" in the globalised economy: cheap - but not quality; just like the priors of clothing (disintegrating after a few washes), consumer electronics (cheap materials), furniture (Instagram-able but utterly impracticable), etc: all made for quick turn-overs to rake in more profit and generate more waste but none made to last long.

joe8756438yesterday at 6:13 PM

Put another way: “reading code costs the same as it always did” arguably more when you consider that the cost of reading goes down when the ability read goes up. in other words if you wrote the thing it is likely you can read it fast. but reading someone elses stuff is harder.

fxtentacleyesterday at 5:54 PM

Scathophagidae are flies that really like eating shit. We know how to cheaply produce massive amounts of shit.

But that doesn't mean we solved world hunger. In the same way, AIs churning out millions of lines of code doesn't mean we have solved software engineering.

Actually, I would argue that high LOCs are a liability, not an asset. We have found a very fast way of turning money into slop, which will then need maintenance and delay every future release. Unless, of course, you have an expert code reviewer who checks the AI output. But in that case, the productivity gains will be max 10%. Because thoroughly reviewing code is almost the same amount of work as writing it.

andrewstuarttoday at 4:37 AM

Understanding computers and programming is not the same as coding.

ChrisArchitectyesterday at 6:10 PM

Related:

Code is cheap. Show me the talk

https://news.ycombinator.com/item?id=46823485

wolfcolatoday at 4:55 AM

i’ve yet to see an agent that can take a figma design and produce high fidelity UI

show 1 reply
manishsharantoday at 4:33 AM

maybe writing code is cheap . But writing unit tests that actually test stuff that matters is suddenly so much more important and expensive.

show 1 reply
d--btoday at 7:30 AM

Well another consequence of that is that you’re going to have a lot more tools to maintain.

And LLMs aren’t half as good as maintaining code as they are to generate it in the first place. At least yet.

simonwyesterday at 6:13 PM

For everyone who is responding to the "Writing code is cheap now" heading without reading the article, I'd encourage you to scroll down to the "Good code still has a cost" section.

octoclawyesterday at 6:01 PM

The interesting thing nobody's talking about here is that cheap code generation actually makes throwaway prototypes viable. Before, you'd agonize over architecture because rewriting was expensive. Now you can build three different approaches in a day and pick the one that works.

The real cost was never the code itself. It was the decision-making around what to build. That hasn't gotten cheaper at all.

show 2 replies
throwaway613746yesterday at 5:43 PM

[dead]

huflungdungtoday at 10:10 AM

[dead]

marcoduvalyesterday at 5:53 PM

[dead]

jsdkkdkdkedjyesterday at 5:51 PM

[flagged]

benakjyesterday at 6:11 PM

[flagged]

show 1 reply