[smogcutter]

But we’re way beyond templates here.

There will be niches in research, high performance computing & graphics, security, etc. But we’re in the last generation or two that’s going to hand write their own CRUD apps. That’s the livelihood of a lot of software developers around the world.

[skydhash]

Do people handwrite those? If you take something like Laravel and Rails. You get like 90% of the basics done by executing a few commands. The rest of it is the actual business logic and integration with obscure platforms.

[prmph]

I hear this denigration of CRUD apps all the time, but people forget that CRUD apps can be as complex or simple as they need to be. A CRUD app is identified as such by its purpose, not the sophistication of it.

Right now I'm wring a web app that basically manages data in a db, but guess the kinds of things I have to deal with. Here a a few (there are many much more), in no particular order:

- Caching and load balancing infrastructure.

- Crafting an ORM that handles caching, transactions, and, well, CRUD, but in a consistent, well-typed, and IO-provider-agnostic manner (IO providers could be: DBs like Postgres, S3-compatible object stores, Redis, Sqlite, Localstorage, Filesystems, etc. Yes, I need all those).

- Concurrent user access in manner that is performant and avoids conflicts.

- Db performance for huge datasets (so consideration of indexes, execution plans, performant queries, performant app architecture, etc, etc)

- Defining fluent types for defining the abstract API methods that form the core of the system

- Defining types to provide strong typing for routes that fulfill each abstract API method.

- Defining types to provide strongly-typed client wrappers for each abstract API method

- How to choose the best option for application- and API security (Cookies?, JWT?, API keys? Oauth?)

- Choosing the best UI framework for the requirements of the app. I actually had to write a custom react-like library for this.

- Media storage strategy (what variants of each media to generate on the server, how to generate good storage keys, etc.

- Writing tooling scripts that are sophisticated enough to help me type-check, build, text, and deploy the app just in the way I want

- Figuring out effective UI designs for CRUD pages, with sorting, filtering, paging, etc built in . This is far from simple. For just one example, naive paging is not performant, I need to use keyset pagination.

- Doing all the above with robust, maintainable, and performant code

- Writing effective specs and docs for all my decisions and design for the the above

- And many many more! I've been working on this "CRUD" app for years as a greenfield project that will be the flagship product of my startup.

[rafterydj]

I don't really disagree with you about handwriting CRUD apps. But I'm not sure that having an off-the-shelf solution, from AI output or not, that would spin up CRUD interfaces would _actually_ erase software as an industry.

To me it's similar to saying that there's no need for lawmakers after we get the basics covered. Clearly it's absurd, because humans will always want to expand on (or subtract from) what's already there.