Live data from Hacker News

Why write code in 2026

softwaredoug.com

1–10 of 321 posts

Re: Why write code in 2026

#7
This is too generic. There's some code I need to write like core abstractions that are going to set the pace for everything. Or tricky steps that can look good without actually working well.

Then there's the mass. I don't need that anymore. The mountains of boilerplate, etc.

I write little islands which need high judgement that are then connected by the obvious goo.

Re: Why write code in 2026

#8
post #4

I still exclusively write my code. The quality is higher. I know exactly how it works. It’s more extensible. You don’t have to generate it.

In fact, it's better not to generate it imo. Like you said the quality is higher, and by the time I get done reviewing the LLM's output I haven't really saved time over just doing it myself. LLMs are only useful for things you can verify extremely quickly (like a short script), or for things where you don't care about the quality.

Re: Why write code in 2026

#9
post #4

I still exclusively write my code. The quality is higher. I know exactly how it works. It’s more extensible. You don’t have to generate it.

In fact, not many people know that these days, but a human doing a thing by bashing their head against it, often tends to improve. My hand-written code is my best yet. My breadth of knowledge, wider than ever.

Re: Why write code in 2026

#10
post #4

I still exclusively write my code. The quality is higher. I know exactly how it works. It’s more extensible. You don’t have to generate it.

In fact, it's better not to generate it imo. Like you said the quality is higher, and by the time I get done reviewing the LLM's output I haven't really saved time over just doing it myself. LLMs are only useful for things you can verify extremely quickly (like a short script), or for things where you don't care about the quality.

Turns out you internalize it when you write it and refactor it with iteration
Post reply on HN