← Back to context

Comment by bonesss

10 hours ago

Generating CRUD is like solving cancer in mice, we already have a dizzying array of effective solutions… Ruby on Rails, Access 97, model first ORMs with GUI mappers. SharePoint lets anyone do all the things easily.

The issue is and always has been maintenance and evolution. Early missteps cause limitations, customer volume creates momentum, and suddenly real engineering is needed.

I’d be a lot more worried about our jobs if these systems were explaining to people how to solve all their problems with a little Emacs scripting. As is they’re like hyper aggressive tech sales people, happy just to see entanglements, not thinking about the whole business cycle.

Go with Laravel and some admin packages and you generate CRUD pages in minutes. And I think with Django, that is builtin.

But I don’t think I’ve seen pure CRUD on anything other than prototype. Add an Identity and Access Management subsystem and the complexity of requirements will explode. Then you add integration to external services and legacy systems, and that’s where the bulk of the work is. And there’s the scalability issue that is always looming.

Creating CRUD app is barely a level over starting a new project with the IDE wizard.

  • >Creating CRUD app is barely a level over starting a new project with the IDE wizard.

    For you, maybe. But for a non-progrmamer who's starting a business or just needs a website it's the difference between hiring some web dev firm and doing it themselves.

    •   > it's the difference between hiring some web dev firm and doing it themselves.
      

      anecdote but i've had a lot of acquaintances who started at both "hiring some web dev firm" and "doing it themselves" with results largely being the same: "help me fix this unmaintainable mess and i will pay you x"...

      jmo but i suspect llms will allow for the later to go further before the "help me" phase but i feel like that aint going away completely...

      1 reply →