Live data from Hacker News

Coding after coders: The end of computer programming as we know it?

nytimes.com

21–30 of 469 posts

Re: Coding after coders: The end of computer programming as we know it?

#21
post #11
post #3

Because they are still making the same salary. In 5 years, when their job is eliminated, and they can't find work, they will regret their decision.

Their decision to... use AI for coding?

Well, their position on AI.

By their own accounts they are just pressing enter.

Re: Coding after coders: The end of computer programming as we know it?

#23
It's really time that mainstream media picks up on 'agentic coding' and the implications of writing software becoming a commodity.

I'm an engineer (not only software) by heart, but after seeing what Opus 4.6 based agents are capable of and especially the rate of improvement, i think the direction is clear.

Re: Coding after coders: The end of computer programming as we know it?

#25

You have to hold AI hand to do even simple vanilla JS correctly. Or do framework code which is well documented all over the net. I love AI and use it for programming a lot, but the limitations are real.

that's just not even remotely my experience. and i am ~20k hours into my programming career. ai makes most things so much faster that it is hard to justify ever doing large classes of things yourself (as much as this hurts my aesthetic sensibilities, it simply is what it is).

Re: Coding after coders: The end of computer programming as we know it?

#27
post #10
post #6

What is a coder? Someone who is handed the full specs and sits down and just types code? I have never met such a person. The most annoying part of SWE is everyone who isn't an SWE has inane ideas about what we do.

Never worked on offshoring projects? That is exactly what the sweatshop coders do.

I think that the current AI tooling is a much bigger threat to offshore sweatshops than to domestic programmers.

Why deal with language barriers, time shifts, etc. when a small team of good developers can be so much more productive, allegedly?

Re: Coding after coders: The end of computer programming as we know it?

#28

You have to hold AI hand to do even simple vanilla JS correctly. Or do framework code which is well documented all over the net. I love AI and use it for programming a lot, but the limitations are real.

Not in my experience. But then again, lots of programmers are limited in how they use AI to write code. Those limitations are definitely real.

Re: Coding after coders: The end of computer programming as we know it?

#29

You have to hold AI hand to do even simple vanilla JS correctly. Or do framework code which is well documented all over the net. I love AI and use it for programming a lot, but the limitations are real.

Not what I've experienced

Re: Coding after coders: The end of computer programming as we know it?

#30
post #9

There is no such thing as "after coders": https://zjpea.substack.com/p/embarrassingly-solved-problems This excerpt: >A.I. had become so good at writing code that Ebert, initially cautious, began letting it do more and more. Now Claude Code does the bulk of it. is a little overstated. I think the brownfield section has things exactly backwards. Claude Code benefits enormously from large, established codebases, and it’…

I spent ~6hrs with Claude trying to fix a web worker bug in a small JS code base Claude made. In the end it failed and I ran out of credits. Claude kept wanting to rip out huge blocks of code and replace entire functions. We never got any closer to a solution. The Claude hype is unreal. My 'on the ground' experience has been vastly different.

Yes, you can get a project with claude to a state of unrecoverable garbage. But with a little experience you can learn what it's good at and this happens less and less.
Post reply on HN