r/AskProgrammers • • 7d ago

The future of Software Engineering is boring

https://packagemain.tech/p/the-future-of-software-engineering

Would you agree?

0 Upvotes

13 comments sorted by

1

u/stanchevdev 7d ago

I doubt it! People will still have to learn the basics and understand the code they're reading, in my experience, it's writing a bit and then mostly debugging. I mean, from what I've noticed, people who use AI sometimes don't prompt properly either, they don't pick the framework, don't make it detailed enough, and don't read what the machine spits out but just paste it in and if it doesn't work, the AI gets a message similar to "It doesn't work, make it better."

I think AI makes it easier to write code, but not necessarily easier to understand what you're doing. You still need to know enough to recognize when something is wrong, and I don't see that changing anytime soon

Your question is very open-ended! In which way and why would it become boring?

2

u/der_gopher 7d ago

But how can you read tons of generated code? It's not as it was before

1

u/zaibuf 7d ago

Simple, we use AI but we dont generate tons of code in one go. More code = more liability. If you go too fast it will just get messy.

1

u/stanchevdev 7d ago

This! Also, in general, I feel like with larger codebases you're not reading millions of lines of code anyway. If you and others have documented what you've built properly, it's a lot easier to navigate. You're not the same person you were yesterday, and if you were to pick up a project after a month, there's a pretty good chance you'd feel lost if you didn't write anything down.

Also yes, there's a difference between existing, tested code and newly generated code, but I don't really see AI generated code as different from copying something off stackoverflow for example. You should understand what you're using and make sure it actually works anyways!

1

u/Lonsarg 7d ago

By NOT generating tons of code.

You can instruct AI to generate less code, less changes, more focused. This requires skill and knowledge about the code, you need to determine on fast glance over generated code where he overcomplicated, where he touched where no touching of code was necessary and then do multiple iterations until you are happy not just with result but with code also.

You also need to determine which parts of code are not that critical and/or are more "brute force not core logic" kind of code. And skip that part (usually UI code, per field mappings from one data model to another...).

1

u/vin_dude9 7d ago

I went to a vibe code conference. Maybe 25% of the people there have no idea about software engineering, they had apps to show case

1

u/baconator81 7d ago

As a software engineer that work with designer/users a lot and constantly trying to come out with new workflow to tackle new problems, I don’t find the future boring, in fact I find the future a bit too overwhelming.

1

u/Dark3rino 7d ago

I used to think that too, but I'm not so sure anymore nowadays.

I am very much anti AI - I honestly feel that it's impacting jobs already and I fear that I'll end up causing a vacuum of seniors in a few years - but I cannot deny that, as a principal, I am even more impactful and can address cross-domain challenges in hours instead of teams spending weeks of work.

Would I exchange this and go back? Any minute - but it's not as awful for me.

1

u/ToucanSam-I-Am 7d ago

I've been programming for 25 years and am more excited about it than ever.

1

u/pvera 7d ago

27 for me. The future is so bright we got to wear shades.

0

u/vin_dude9 7d ago

I’m learning OS code, more accesible with AI, so that’s not boring. I also recently used AI to one-shot a heads-up game-style phone game. I didn’t even see the code at all, it just worked. For that project I didn’t even engineer anything, but the outcome was fun.

1

u/der_gopher 7d ago

you describe the generation part is fun, I agree. but as a profession, is it? are you a professional programmer?