3 ms·
> ...the dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff No. I see this a lot on HN, the idea that "CRUD" applicati
by crispyambulance 7y ago
> ...the dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff
No.
I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. It simply is not true.
I think folks are just extrapolating from "Pet-shop" or "Northwind" examples that they've seen in tutorials/docs and assume that that is what, say, enterprise developers actually do at the same level of complexity. It's not and it has never been the case.
- scarface74 7y agoCRUD apps are simple. You need one or two architects and seniors to make sure that things don’t go off the rails and to gather the requirements and once you have that, some boot camp grads can do the grunt work. When I was a team lead, I wouldn’t overpay for a crud developer. I call myself an “enterprise developer/architect” on HN for context - meaning I don’t work for the cool hip startups but let’s call a spade a spade, I’ve spent the last 10 years working on yet another software as a service crud app or bespoke internal apps. Yeah I spend some time in meetings, dealing with “cloud native” infrastructure and I can hold my own up and down the stack.
- ThrowawayR2 7y ago> I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. Nah, it's true. For the average small to medium size company, CRUD apps are mostly "plug library A into framework B, with a dash of glue logic" and you're done. The most difficult part is the yak-shaving needed to get things to work together. Things like embedded systems or scaling to FAANG levels are much more difficult.