[pkdpic]

I like this as a narrative framework a lot more than the AGI arc. This seems a lot more realistic and less dramatic, more human-focused.

I like the idea of a model being able to create and maintain a full codebase representing the app layer for model-based tools but in practical terms at work and on personal projects I still just don't see it. To get a model to write even a small-scale frontend only app I still have to make functions so atomic and test them to the point where it feels close to the time it would take to write the app manually. And if I ask a model to write larger functions or don't test them / edit them through 3-5 rounds of re-prompting I just end up with code debt that makes the project unrealistic to continue building out beyond a pretty limited MVP stage without going back line by line and basically rewriting the whole thing.

Anyway I'm no power user, curious what other people's experience is. Maybe I'm just using the wrong models.

[lubujackson]

I think the extrapolation is that the "back and forth" process is what is being improved quickly now. The trade-off is that you don't get a function back but you define a project and AI, with a focused model, will understand and handle all the back and forth until the project works and meets the specifications reasonably well. So it really is looking like a vibe coding future.

I think where things get interesting is that obviously lots of businesses and products won't be built this way, but there will be a lot of reasons to shave off sections of a core business to be "vibe-able". So a new level of rapid MVP will be possible where you can spin up completely functional apps multiple times a day, maybe even dynamically generate them. Which leads to more modular app integrations as a default.