Live data from Hacker News

The End of Programming

pauldix.com

1–10 of 124 posts

Re: The End of Programming

#3
I don't know if this is the end of programming, but i can clearly observe the gradual end of expertise in my company - people slowly forgetting architecture, principles, and how stuff works in general, in favor of code delivery speed.

And without expertise you end up asking stupid things to a token producer machine, however godlike it can be.

It's hard not to extrapolate...

Re: The End of Programming

#5
Nope. Not yet. The frontier still produces slop and never refactors. Your code base will grow with the square of your features and grind to a halt. God speed to folks that work at this shop.

Re: The End of Programming

#8
post #5

Nope. Not yet. The frontier still produces slop and never refactors. Your code base will grow with the square of your features and grind to a halt. God speed to folks that work at this shop.

You can often just tell it to refactor though. That's like a scheduled harness thing, not a game changer.

Re: The End of Programming

#9
This is a strong article with a distracting headline. Challenge for commenters: can you discuss the content without getting caught up in the headline?

My favorite paragraph:

> The fact that AI wrote 1M LOC and then refined it over the course of the next couple of months to produce a reliable piece of software that is currently running on millions of developer machines is absolutely mind blowing. And you can say, “well it’s not that impressive because they had an oracle to compare against, so it was simple to go from one language to another”, but I think that’s selling this entire thing short. If you can build a verification system and give proper direction, AI can produce a highly complex, highly sophisticated piece of software and it can continue to refine it until it just works.

For me, this captures what's special about the Claude Fable 5 and GPT-5.6 Sol class of models. If you can reduce a problem to a clearly verifiable end state, provide the necessary context, and equip a model with the necessary tools it can usually get to a good solution.

Reducing problems to that state and designing that environment remains a skill, and one that I expect we will be paid handsomely for.

Re: The End of Programming

#10

I don't know if this is the end of programming, but i can clearly observe the gradual end of expertise in my company - people slowly forgetting architecture, principles, and how stuff works in general, in favor of code delivery speed. And without expertise you end up asking stupid things to a token producer machine, however godlike it can be. It's hard not to extrapolate...

I guess in most industries speed was always the primary concern. Things like architecture and principles were there only to prevent things slowing down to a crawl. A way to protect that speed
Post reply on HN