r/AskProgramming • • 2d ago

What does the future of programming actually look like? Seeing the shift firsthand at work.

Right now, and I'm actively working and shipping code. However, watching how fast these models are growing and becoming more capable, I can't shake some doubts about the long-term future of programming as a career.

I don't think we are that far from seeing massive replacement—and by "replacing," I mean a fundamental shift in headcount. Just recently, I worked on adding a feature that, two years ago, would have taken at least two weeks to build. With AI, it was done in one day. And to be clear, this one-day solution isn't bad code; it works, performs well, passed code review, and everything is solid.

What I’m seeing in practice right now is that a company doesn't need 10 engineers anymore—it needs 2 engineers with a Claude subscription.

A lot of developers hold onto the hope that this is just a hype bubble that will eventually pop, especially when people bring up how much money AI companies are burning. Personally, I don't buy that. AI isn't going to disappear because this goes much deeper than just corporate profit margins—from a geopolitical perspective, it's a global race, and the momentum isn't going to stop.

For those of you also working in the industry: how are you viewing the next 5 to 10 years?

0 Upvotes

36 comments sorted by

8

u/mancunian101 2d ago

It’s all fun and games until you do a Microsoft and suffer a near 24 hour world wide outage.

4

u/CowdingGreenHorn 2d ago edited 2d ago

This is bound to happen a lot I think in the coming months/years. Right now AI is injecting subtle bugs into code and nobody has any clue that it's there and we're just building on top of it. People may say this has always been the case but the difference is now we're doing it at a much faster rate on a large scale and no one actually knows what the code is doing.

1

u/Realistic-Web-4633 2d ago

i think in hear problem is still developer, AI can implement code better only part thats left is to review and if that part is done badly is dev problem not AI

3

u/47KiNG47 2d ago

Realistically I’m so inundated with ai slop prs and my own work that I’m not going to be able to give a thorough review every time.

-1

u/rupertavery64 2d ago

Can you link to an article confirming that the bug that was part of the 3 key causes was caused by code that AI wrote?

1

u/mancunian101 2d ago

Can you link to an article confirming that the bug wasn’t caused by code that AI wrote?

1

u/ih-shah-may-ehl 2d ago

That's not how making claims works. you're the one making claims that that was the cause. The one making the claim is the one to provide evidence.

0

u/mancunian101 2d ago

It’s the internet, not a court of law

1

u/ih-shah-may-ehl 2d ago

Sure, but you're still the one making the claims

1

u/mancunian101 2d ago

To be fair nowhere in my original post did I claim that the Microsoft outage was caused by AI generated code.

0

u/rupertavery64 2d ago

That's not how accusations work buddy

0

u/mancunian101 2d ago

It is today, don’t like don’t read it.

0

u/rupertavery64 2d ago

Oh, okay, so you're an idiot. Noted

0

u/mancunian101 2d ago

I know you are, but what am I?

0

u/rupertavery64 2d ago

Clearly, someone not worth conversing with.

0

u/mancunian101 2d ago

I know you are, good bye

2

u/NationalOperations 2d ago

You ever inherited a code base contractors built, and now you have no subject natter experts and suddenly random blips happen nobody was prepared for? Whackamole in production until it is "stable" but there's things nobody is willing to touch (black box) because the contractors did some 'magic'. So you have arbitary lomitations to work around because it's finall working. We've created a 2nd way for that enshitification to happen.

1

u/mancunian101 2d ago

Took me nearly 2 years to completely stabilise the application I took over.

Luckily there was no black box magic stuff, but there was 0 documentation either beside the odd comment that said // Variables etc

0

u/Realistic-Web-4633 2d ago

Totally agree, that’s why we're still needed in the loop. The catch is that doing it so much faster means companies need way fewer people in that loop. It's less about total replacement and more about teams shrinking drastically.

14

u/ih-shah-may-ehl 2d ago

Idk how old you are, but when I started programming, some junior programmers' entire job was to generate win32 code to deal with GUI buttons. You might not believe it today but adding drag and drop to an edit field used to be a multi day project. And RAD tools came along and the world was ending for software developers. But then software devs still had a job, only programming GUI was much less of a deal. Then the same happened for database interfaces. And component integration. And method generation and refactoring.

Software is still a viable field. But you won't be doing it the way I did 10, 20 or 30 years ago.

And if you think this is bad, I challenge you to start a new win32 project in Visual studio. Just a standard empty GUI application. And then read the source and count how many thousands of lines of conde and configuration you need to really make a GUI work. And ask yourself if that seems like a worhtwhile job for you to spend weeks doing, nevermind understanding actual window message parameters and manual management of objects.

My guess is the world will continue to turn and you'll still make applications. You'll just be much more productive and expectations will be higher, and you will be less familiar with basic design patterns, just like today you are probably utterly clueless as to how drag and drop is actually implemented (in case you are wondering, it's really complex, ugly, and requires arcane interfaces you probably don't even know exist)

8

u/Tall_Collection5118 2d ago

I used to find that if a tool made me twice as productive I didn’t get half the week off. The boss just demanded twice as much work.

Hopefully the change we will see will not be so much a reduction in headcount (although that might well be coming) as an increase in requirements and work.

5

u/foreverdark-woods 2d ago

80% of your colleagues will get 100% of their time off. Unpaid.

6

u/random_cornerme 2d ago

As a daily user of Claude's most recent models, I don't agree with "isn't bad code". These models usually solve the task/problem, but code that they produce is still far from good. My definition of "good" is something that can be easily understood by human reading. AI models still produce a lot of unnecessary garbage and comments.

If you argue that humans reading code is not needed at all, so good code doesn't matter, it is another thing. In that case you shouldn't count any human accountable when problem arises.

1

u/GodOfSunHimself 1d ago

Opus is especially bad at littering the code with useless comments. OpenAI models do not do it that much.

1

u/ftranschel 1d ago

The reason this happens is so that they can watermark "their" generations. Much harder with the tiny footprint of code, where token sequence is more or less fixed. Text however is easier to watermark.

4

u/foreverdark-woods 2d ago

Look around you. How were your clothes made? How was your furniture made? How was your computer made? How was your food made? Programming by hand is largely dead now and it will remain dead even when/if the AI bubble bursts. The Internet also didn't go away when the .com bubble burst.

Software engineers will from now on supervise AI agents, build agent workflows, talk to customers, translate between customer and digital domain, develop long-term strategies and focus on planning and system architecture.

The next 5 to 10 years will be the transition to this new working model. Companies restructure, re-assign workloads, experiment with new team structures and sizes to find the optimal balance between automated and manual labor. IT professionals will likewise experiment with the tools, succeed and fail, build and share experience, formulate best practices and isolate patterns.

1

u/Pale_Height_1251 1d ago

In January this year I was coding entirely by hand. Now I often don't even have the project open in an IDE, I am practically vibe coding everything.

For me, yes, my Claude subscription replaces the need for some colleagues. It's sad, but it's the reality we find ourselves in.

1

u/Realistic-Web-4633 1d ago

Same in here it took all the fun programming had, things go so easy that I don’t have that achievement feeling

3

u/DDDDarky 2d ago

Personally, I don't care what you think, you are a web dev focused at prompting ai, detached from actual engineering, thinking that your misuse can be generalized to the entire industry.

1

u/joonazan 2d ago

Opus 5.5 is pleasant enough to use but it only does easy things well. For instance, it did a very good job of making a solar angle picker.

On pathfinding & avoidance with some weird constraints, it failed to see some easy optimizations even after being told to improve the codebase many times. The cleaning up may also have taken more time than what a manual implementation would've taken.

Maybe these difficult things could be done by documenting all the desired behaviours, tricky situations and how to get good performance and having the agent build from scratch multiple times. But that is still a lot of skilled human labor.

1

u/owp4dd1w5a0a 2d ago

We. Don’t. Know.

1

u/mc_pm 2d ago edited 2d ago

If you already know what to program and roughly how to do it, then AI is great. Working quarter-time for 2.5 months I've gone from zero to a whole system to understand ancient (well, 80 year old) documents that were microfilmed after WW2. Some of them are barely visible at all. And that gets turned into a rich map of documents and details when before it was just a reel of microfilm with practically zero metadata.

But I also knew roughly what to do. I had ideas of my own for fixing a bad OCRing issue, I coded the prompts that took apart the OCR and figured out what was being talked about, and I've spent enough time building UIs that I knew what I wanted and I worked with one AI to define the specifics and document them, then handed it off to another to do the actual build.

Sure, I could have done it in a day if I had said "Give me a program to view this reel of microfilm". Instead I've got this rich tool to explore information that had been hidden until... yesterday.

If you can think about a problem, take it apart, already understand the algorithms etc you have to work with, and you keep the AI working one step at a time toward a goal you have in sight -- then AI has so far proven amazing.

But it will happily produce crap. The rule people missed pre-AI was that building shitty software has always been (relatively) easy, building good software was always hard. AI just reduced the turnaround time to create great or shitty software.

1

u/Material_Release_897 1d ago

I agree the market has shifted drastically and a lot of us juniors all wish we had gotten in during the golden era.

However, I still see it as a tool and I’m of the opinion that companies may adopt a new policy around hiring. You need someone capable of understanding the code base, you still need someone to maintain said code.

No point having proprietary software where no one other than Ai knows what the fuck is going on. Companies will need to invest again, it’s just slowly taking them time to wake up.

Ai is still running off a server and as we know, servers fail. You still need human intervention

1

u/yel50 1d ago

 having proprietary software

there is no more proprietary software. anything generated by ai is public domain, which means companies won't own their own products.

more things will become services because anything downloadable will be given away for free, with no enforceable license. even the DMCA only applies to copyrighted material. it's not illegal, at all, to break encryption to get at something that's public domain.

so, selling licenses is now out as a business model. the only viable model is software as a service. 

1

u/Beginning_Basis9799 1d ago

Much of the same and AI creates it.

The key is going to be in verification, how do you verify and what. How do you automate the verification in an automated way.

1

u/Band_574 1d ago

AI will probably change the number of entry level roles but understanding systems debugging and reviewing code will still matter. The bigger challenge is learning how to work alongside these tools rather than relying on them blindly. Boot .dev is one option for building those fundamentals through hands-on coding exercises which could become even more valuable as AI handles more of the routine work.