[torben-friis]

Generation and maintenance are very different beasts.

There are engineers that work making a 2 weeks app that is never revisited again, I guess, but I don't know anyone that makes a living from that. Maybe the "WordPress site for your business" gigs.

The issue comes when you have 432 functionalities and have to add the 433 without interfering with the others. Or when you cant afford slightly wrong. Or when each functionality adds complexity at a higher rate than an engineer and over time the projects gets to an unmanageable size.

[slyzmud]

> The issue comes when you have 432 functionalities and have to add the 433 without interfering with the others. Or when you cant afford slightly wrong. Or when each functionality adds complexity at a higher rate than an engineer and over time the projects gets to an unmanageable size.

But that's not a problem on small projects. non-technical people only create software to scratch their needs, they will probably will need 20 or 30 features, never 432, making their system much easier to handle.

The problem with enterprise software is that it has to support a very large combination of features designed for different clients. That's why it gets so complex, but if the software has to support a single client is waaay easier.

[torben-friis]

Sure, there's a place for disposable, ultra custom apps that AI can cover. I vibecoded one to help me clean up my local media with a tinder-like UI for discarding/keeping photos, for example.

That's not going to substitute many engineers though, for two reasons.

One is that "app that helps a single-digit number of people" was never a viable business in the first place.

The other is that you can't substitute all corporate software with a combination of disposables. Some stuff is complex even if the "surface features" are small in number. Say for example that you want a custom web browser, "surfing the internet" might feel like a single feature for a non technical person but it's made of many moving parts inside.

[Yokohiii]

I mean that is a classic problem right? We know that outsourced green field projects done by third parties are tend to be low quality or at least are slow and expensive to integrate into a business. Many issues arise when you try to deploy these projects and more show up once it is out. Eventually there is someone reasoning how to fix the problems. An LLM wont do it on it's own, there are too many invisible constraints.

One can argue that software engineering will fundamentally change, but there is and will still be a need for people that know what software engineering is and how to apply it.