Two of my favorite parts of CRUD are the data modeling and interface design. There are certain CRUD interfaces that will end up with thousands of user hours in them. It's important that they're good.
Business folks have input, but often you the programmer are on the hook for the data model. The best data models can be incredibly resilient yet evolvable across the lifetime of the business. They'll define how people think about and process the entities in your system for years to come.
Same for user interfaces. People have spent thousands of aggregate hours in CRUD that I've built doing jobs to support themselves and their families. It's the little affordances that make systems reliable, effective and maybe even kinda fun to use as an end user.
Also you can fuck both of the above up really badly and see cascading negative consequences for years... I've definitely needed a few oopsies to learn just how important CRUD decisions can be.
> People have spent thousands of aggregate hours in CRUD that I've built doing jobs to support themselves and their families. It's the little affordances that make systems reliable, effective and maybe even kinda fun to use as an end user.
Agree with all you said, but this really hit home. It’s incredibly fulfilling to see and work with people spending thousands of hours in your app while your team continually improve it.
I like writing CRUD apps. The best part is when you've been doing what you would do if you weren't getting paid and you get to say "fuck you pay me".
That's all this is, searching and sorting and a UI on top of it. CRUD apps.
It ain't computer science.