News for hackers. Stuff that matters.
Re:Ask HN: How to avoid being a pragmatic programmer? by js8 on Friday October 21, 2022 @08:53AM (#33287480)
> Typically, the company hires experts to do the same thing over and over again.

To me, the biggest mystery is why IT keeps tasking programmers with mundane and repetitive tasks when, unlike in other professions, the beauty of programming lies in the fact that you can abstract and automate the repetition.

Why we need million programmers building CRUD apps, why they don't have a standard already?

Re:Ask HN: How to avoid being a pragmatic programmer? by BlargMcLarg on Friday October 21, 2022 @09:02AM (#33287564)
Legality and stubbornness.

Same reason we have dozens of languages with very minor differences (not different paradigms), endless discussions on formatting despite opinionated linters/formatters existing, bike shedding meetings, and more.

Re:Ask HN: How to avoid being a pragmatic programmer? by badpun on Friday October 21, 2022 @09:47AM (#33287953)
I think we have a standard for the most part. Most of the work being done today is around expressing business requirements in code. The technical side of the tasks is automatically handled by web frameworks, database engines etc. behind the scenes.
Re:Ask HN: How to avoid being a pragmatic programmer? by ipaddr on Friday October 21, 2022 @10:52AM (#33288600)
The standard exists it is called wordpress and powers most sites.
Re:Ask HN: How to avoid being a pragmatic programmer? by saltcured on Friday October 21, 2022 @11:36AM (#33289137)
To me, this sounds a bit like asking why we still have word processors and printers when photocopiers already exist.
Re:Ask HN: How to avoid being a pragmatic programmer? by Tarucho on Friday October 21, 2022 @11:54AM (#33289385)
Because what gets built is the knowledge of the system. The CRUD part is an implementation detail.
Re:Ask HN: How to avoid being a pragmatic programmer? by Viliam1234 on Friday October 21, 2022 @04:31PM (#33292705)
There are multiple reasons. One of them that doesn't get mentioned much is the incentives of managers. If your team reinvents the wheel, it makes you a "technological leader". Customizing an existing standard would mean that the company does not actually need a team of developers, one of them would be enough, which implies that the company does not need you.

People keep talking about how the programmers often choose technologies to advance their own CVs, as opposed to doing what is the best for the company. Guess what, managers do analogical things all the time. It is the most reliable way to climb up the corporate ladder.