Top
Best
New

Posted by softwaredoug 2 days ago

Why write code in 2026(softwaredoug.com)
90 points | 140 commentspage 3
hirvi74 2 hours ago|
I write organic code in 2026 because I do not have a choice. Which, honestly, I am thankful for most of the time. My employer has no LLM mandates nor do they supply us an LLMs to use.

In my personal life, I cannot justify more than a $20 sub per month. I only use the Web Chat anyway. Shelling out $100-$200 a month for a sub in which I would get little to no ROI is a poor choice. Besides, I've never hit the limit on my $20 a month plan either.

The day I am forced to prompt LLMs all day, every day is the day I am cashing out of programming as a career. Though to be clear, I have no opposition towards anyone that uses LLMs, and think they are fantastic tools when used appropriately. (I love them as a StackOverflow replacement, and have learned a lot from going back and forth with LLMs).

conqrr 6 hours ago||
All this debate around use LLM or not is tiring and just black and white thinking.

Can I use agents to code a SWE project? yes, with nuances.

Can I write code for a SWE project? yes, with nuances.

Its more options now, I'll write code about projects I deeply care and will use llm at work where its shared slop and forced usage.

jonplackett 18 hours ago||
Prediction: in 2027 a coding agent will read this as inspiration for why it should code.
sublinear 17 hours ago||
> If we’re building a software factory, details matter. The details that establish architectural patterns. Down to algorithms and performance. Agents push us to evaluate, measure, and guard. They’ve made it cool to add CI into side projects early, not as an afterthought. That’s massive improvement to the state of software.

Why are you building a software factory though, and why weren't you immediately adding CI to every project?

> 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.

Again, why? Where are you working where this is considered a good idea? This would mean that the software engineers are not just being completely kicked out of all business decisions, but asked to build a moat that ensures they stay on the other side of it.

Any business that intentionally devalues the insights gained through implementation will eventually starve itself to death by making too many passive thoughtless moves. No insight will ever be gained just spot checking AI. Is their intention really just to make tiny amounts of profit while riding the thing into the ground? Crabs in a bucket, man.

slopinthebag 6 hours ago||
Seems like there’s broadly two ways to use LLMs for coding - either as a way to generate the same code you would have written but faster, or as an opaque program-generator where you have no idea what the code is doing. One of these methods results in roughly the same amount of understanding and the other one radically less.
rdksu 5 hours ago||
exactly how many times do you plan on posting this here
minimaxir 5 hours ago||
https://news.ycombinator.com/item?id=48883660
vips7L 20 hours ago||
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.
sph 19 hours ago||
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.
bigstrat2003 19 hours ago|||
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.
glouwbug 18 hours ago||
Turns out you internalize it when you write it and refactor it with iteration
lordnacho 15 hours ago||
But the attraction of LLM code is not that you get quality.

The selling point is that you know have a quality Vs time tradeoff that is a lot better than you used to have.

I can spend 10 seconds typing out a prompt that will generate ok code.

Before a couple of years ago, it might have taken me an hour to type out and debug that code.

vips7L 12 hours ago||
Sure, if you prefer low quality go ahead. Many people have always preferred low quality. Many people prefer to eat junk. I also genuinely believe that time tradeoff doesn’t matter.

> Before a couple of years ago, it might have taken me an hour to type out and debug that code.

Are you not running and testing your code?

lordnacho 10 hours ago||
It's just naive to say you are always going for quality. Everyone has constraints in money and time that they need to think about.

> Are you not running and testing your code?

Why would you think that?

vips7L 9 hours ago||
> Why would you think that?

Because you’re claiming to not debug, and that you’ve gone from 1 hour to 10 seconds. I can only go off of what you tell me here.

mikkolaakkonen 9 hours ago||
The software factory is exactly what I'm building. The world is changing, we can either be the ones changing it or be forced to change afterwards.
light_hue_1 19 hours ago||
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.

sublinear 17 hours ago||
The boilerplate was always boilerplate though. You never needed to write it to already have that code in your project, so I'm confused by what you mean.

Generating boilerplate is strictly inferior than something already written and tested by the authors of the tools. You will eventually have to make slight adjustments to it, and those decisions can be just as impactful as your "high judgment" code. Those decisions are what actually enable your high judgment code to stay clean and straightforward.

Poor decisions in code architecture are some of the biggest blunders of all. Once you have begun to fill in the blanks on some boilerplate code, it ceases to remain boilerplate code. If you let AI make those adjustments, you will eventually blunder the codebase in precisely this way. You'll first recognize it when your high judgment code seems too verbose. You'll then soon realize some things are impossible without adjusting the boilerplate you started off with. Then the AI will fail to grasp what you want and you'll have to manually untangle a lot of the slop that you let grow out of control. Good luck with that.

jdthedisciple 17 hours ago||
this is the way
More comments...