Live data from Hacker News

Why write code in 2026

softwaredoug.com

291–300 of 321 posts

Re: Why write code in 2026

#291

"Why write code in 2026".. Because AI generated code is STILL complete ass. Even Fable, even whatever custom Pi/opencode leet code harness you have, the output is awful, and, if you cannot distinguish the quality of your code vs the AI's, I've got some bad news for you.

My code is/was worse than AI's, but at least I get paid, so what do I care about the bad news you have.

You are exactly the person who should be afraid then and you prove his point?!

Re: Why write code in 2026

#292
post #97

>It’s our job to build the software factory - not just the software. Software engineers maintain the assembly line allowing anyone to prompt for a change and ship immediately. The job of the software engineer increasingly becomes to make himself unnecessary: to empower the nontechnical business users to do as much as reasonably possible, without his/her intervention. This has, of course, been the dream of computing,…

This isn't the first or even the tenth attempt at making computer programming accessible to everyone. Remember COBOL? COBOL made the computer speak English. It didn't help.

A specification detailed enough to control every aspect of the resulting product is called a program. Compilers are AI. The prevalence of compilers hasn't harmed the programming industry at all, quite the opposite.

Re: Why write code in 2026

#293
post #44

Earlier quoted context omitted.

> and no different than copy and paste from stack overflow This isn't really the point of your comment, and for that I apologise, but: not all of us did that. For many good reasons, too.

> not all of us did that. For many good reasons, too. This isn't really the point of your comment, and for that I apologise, but I still haven't gotten used to speaking about what we "used to do" in the past tense, as if we are in a post-programming world... We are already starting to speak of the habits we used to have (or not have), how things used to be done back in the day (1-2 years ago). I don't think you're wr…

Objectively, the usage metrics at Stack Overflow are showing that it is already dead. Very few people are still accessing it for any reason. While programming might not be in the past, Stack Overflow very much is.

Re: Why write code in 2026

#294
post #276

Earlier quoted context omitted.

Ah, well... I can't say that there's any real hope. I dove in in ~2023, and I'm about as deep in it as one can be. The better I get at it, and the better the agents get, the less time I spend even doing what I do - one prompt will often take 3+ hours. I often keep 8+ agents churning for the whole workday (and leave them running when I leave, too, and it's very often that they'll work from 4pm to midnight or later). I…

May I ask what you end-up doing for the rest of the day?

Depends on the day. Mostly playing with the applications I'm developing to try and find gaps or rough edges, or reading over code and developing further AI tooling when I find disgusting code (to try to detect/fix/prevent disgusting code of that nature). Also, talking to coworkers to learn about the products we build and the business we're in.

Re: Why write code in 2026

#295

Earlier quoted context omitted.

Just interesting to see Claude’s hourly rate is around $17. Much cheaper than a human software engineer. But comparable to the wages for some human workers.

As soon as human software engineers are Ubered away from the field, the price will ramp up to that of a human software engineer or more, have no doubt. ROI won't make itself up.

Let's hope open models will continue to improve and avoid the price ramping.

Re: Why write code in 2026

#296

Earlier quoted context omitted.

Oh that's an interesting thought. Goto's are considered harmful, because holy hell as a human trying to understand and reason about code, the spaghettifcation if someone else used gotos all over the place and I have to reconstruct their thought process just doesn't sound like fun. But if we're no longer writing code by hand (which, I gotta be honest, I'm using AI to write a lot of code for me these days), then does t…

Compilers only really use them for things like break and the end if blocks. There isn't much to gain by being able to execute anything arbitrarily, and then go...where? There might be places here and there within a function where compilers already take advantage of it, but I doubt it's useful in the way you think.

in C it's quite normal to set a return code and jump to a cleanup section where all the buffers are freed, all the files closed and so on.

Re: Why write code in 2026

#297
post #93

Earlier quoted context omitted.

If you think we're "done", you have no imagination.

What are you gonna make? Yet another CRUD app? An API subscription? A game? A mobile app? We’ve created software for virtually every place we can put software. There’s nothing new. It’s like bridges. We’ve seen all the ways bridges can be built by now. There’s nothing new left to discover.

Well, a short time ago somebody made the first LLM. Was that the end of it?

Re: Why write code in 2026

#298

"Why write code in 2026".. Because AI generated code is STILL complete ass. Even Fable, even whatever custom Pi/opencode leet code harness you have, the output is awful, and, if you cannot distinguish the quality of your code vs the AI's, I've got some bad news for you.

99% of code ever written has always been shit. Most of it has been thrown out or not in use anymore, or EVER used. Most people arent going anything particularly unique or complicated or performance focused.

Re: Why write code in 2026

#299

Earlier quoted context omitted.

Oh that's an interesting thought. Goto's are considered harmful, because holy hell as a human trying to understand and reason about code, the spaghettifcation if someone else used gotos all over the place and I have to reconstruct their thought process just doesn't sound like fun. But if we're no longer writing code by hand (which, I gotta be honest, I'm using AI to write a lot of code for me these days), then does t…

I assume there's a clear technical reason why GOTO is harmful, it adds to the complexity of the code, makes it harder to understand and fix and evolve. Wouldn't the same difficulties affect the LLMs ability to understand and fix and evolve the code as well?

As a human with a human level of working memory, the number of things I can keep in my head and map to concepts and functions is unfortunately limited. An AI running on an Nvidia supercomputer has higher limitations on what it can hold in its working memory, so could theoretically handle more than my human brain can.

Re: Why write code in 2026

#300
post #239

Earlier quoted context omitted.

Until winter.

Humans have been storing food for winter for hundreds of thousands of years before agriculture and the invention of writing, you think they all died off or something? People whose crops failed instead were more heavily affected in winter than hunter gatherers.

Of course, but the surpluses made possible by agriculture meant occasional starvation became a much rarer event
Post reply on HN