Live data from Hacker News

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

nytimes.com

391–400 of 469 posts

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

#391

Earlier quoted context omitted.

If managers can't understand why this isn't a brag, then your job is hardly safe.

Managers jobs are more at risk than senior engineers. My company, and few others I know reduced the number of managers by 90% or more.

if the industry got rid of 98% of the managers - the industry's output would go up by 500x

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

#392
post #379

Earlier quoted context omitted.

Eating is also not really optional If you're going to spend a pretty good chunk of your lifetime eating, you might as well get good at it so you can enjoy the food you make

Do you want to eat good food or make good food? Is doing the dishes something you hand to a machine or do you always do it by hand? Are there any ingredients you buy pre-made (pesto, curry pastes, do you make your own panko breadcrumbs)?

Aren't you proving the point that it's nuanced?

Thread seems to be saying LLMs are great because they do the dirty work and leave the fun work to humans. The counter-point is not exactly that LLMs aren't capable of doing dirty-work, it's that the nature of work isn't going to split so cleanly.

And cooking is a good example. Cooking is work. And slop. And it's also incredibly rewarding and creative, if you want it to be. Robots can help along that entire journey.

Maybe this is the core point: "cooking is a solved problem" that's how engineers always think. Except it's not. And 100% automation is still not going to break that discussion so cleanly.

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

#393
post #379

Earlier quoted context omitted.

Eating is also not really optional If you're going to spend a pretty good chunk of your lifetime eating, you might as well get good at it so you can enjoy the food you make

Do you want to eat good food or make good food? Is doing the dishes something you hand to a machine or do you always do it by hand? Are there any ingredients you buy pre-made (pesto, curry pastes, do you make your own panko breadcrumbs)?

My point, which you seem to have missed, is that people have an intrinsic incentive to care about learning to cook because eating is something we have to do every single day regardless

No such incentive exists for building software

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

#394

For me, the biggest shift is people who don't care about local AI. The idea that you can no longer code without paying a tax to one of the billion $ backed company isn't sitting well.

The marginal differences in quality seem pretty meaningful right now, enough to make Claude wildly dominant, but some of the locally runnable models like Qwen feel only a few months behind the leaders. I'm betting the generational gains level off and smaller local models close the gap somewhat. Then harnesses will generally be more important than model, and proprietary harnesses will not offer much more than optimiza…

Qwen3.5 really is great.

But the biggest thing is going to be context. Whilst a 10gb card can run a 9b model with some context .. for coding you really want a lot of context.

So if paying 200 a year for 1T in context, vs your 32k context.. that's the thing I see as being the driver.

Personally ive found great success with using open code, having Opus as my plan agent, and omnicoder-9b as my build agent.

Get opus to plan, switch to omnicoder to build, switch back to opus to review. Etc etc.

Works great.

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

#395
post #392
post #379

Earlier quoted context omitted.

Do you want to eat good food or make good food? Is doing the dishes something you hand to a machine or do you always do it by hand? Are there any ingredients you buy pre-made (pesto, curry pastes, do you make your own panko breadcrumbs)?

Aren't you proving the point that it's nuanced? Thread seems to be saying LLMs are great because they do the dirty work and leave the fun work to humans. The counter-point is not exactly that LLMs aren't capable of doing dirty-work, it's that the nature of work isn't going to split so cleanly. And cooking is a good example. Cooking is work. And slop. And it's also incredibly rewarding and creative, if you want it to…

The comment I was responding to was looking at a state where we looked at markdown files instead of programming, my point was to agree with the original quote that they can remove the drudgery.

> Maybe this is the core point: "cooking is a solved problem" that's how engineers always think.

But it isn’t, that’s a lazy stereotype of a subset.

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

#396
post #151

Earlier quoted context omitted.

The two types of coder argument seems strong to me. Coders who love the art of programming (optimisation for the sake of it, beautiful designs, data structures...) and builders. The former are in for a rough time. The latter are massively enabled and no longer have to worry about smashing together libs by hand to make crud apps.

Imagine if your operating system or compiler were written by the sort of person that thinks " Coders who love the art of programming ... are in for a rough time. "

Yeah but 99% of jobs are decidedly not that.

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

#397
post #379

Earlier quoted context omitted.

Do you want to eat good food or make good food? Is doing the dishes something you hand to a machine or do you always do it by hand? Are there any ingredients you buy pre-made (pesto, curry pastes, do you make your own panko breadcrumbs)?

My point, which you seem to have missed, is that people have an intrinsic incentive to care about learning to cook because eating is something we have to do every single day regardless No such incentive exists for building software

No such incentive exists for an enormous amount of what humans do.

People don’t only build software because they have to.

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

#398
post #252
post #151

Earlier quoted context omitted.

The two types of coder argument seems strong to me. Coders who love the art of programming (optimisation for the sake of it, beautiful designs, data structures...) and builders. The former are in for a rough time. The latter are massively enabled and no longer have to worry about smashing together libs by hand to make crud apps.

Doordash has also enabled home cooks; they no longer have to worry about smashing together ingredients by hand to make dinner. They just prompt the app to make them the food they want. Doordash is the future of home cooking.

Prepackaged pasta sauces and cake mix. Worse than making it from scratch but enables people with no time to cook more dishes.

Doordash is more like paying someone else to code for you. Luckily that will soon be a thing of the past.

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

#399
post #151

Earlier quoted context omitted.

The two types of coder argument seems strong to me. Coders who love the art of programming (optimisation for the sake of it, beautiful designs, data structures...) and builders. The former are in for a rough time. The latter are massively enabled and no longer have to worry about smashing together libs by hand to make crud apps.

"bvilders" right now its mostly people who want to build a substandard app and shill it everywhere.

That's what's visible now. Give it more time and larger, more long-term projects will come out. I'm talking about people with ambitious ideas who -could- code but lack the time or energy.

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

#400
post #378
post #262

Earlier quoted context omitted.

amidst this whole AI craze it's illuminating to learn how many programmers secretly hated programming all along

This is exactly how I feel. I knew it already to an extent from my time in college, but so many people come into this industry because they want to be able to produce the end product, or just have a stable job that makes good money. Neither of those are bad reasons to get into this profession, but it does make me sad how few peers I have who do programming because they're passionate about the act of programming. The…

Aside from many of these things just being a layer difference - it’s not unreasonable to want to work on databases query optimisation an not enjoy css or enjoy building frontends but just want a db that’s fast and works. The flip of your view is that they may find it sad that you don’t want to make things, you just want to solve puzzles.
Post reply on HN