News for hackers. Stuff that matters.
Re:Kernighan and Pike were right: Do one thing, and do it well by benj111 on Saturday August 19, 2023 @04:13AM (#37186653)
Suggestions for a term for the phenomena?

Emshitifaction?

Re:Kernighan and Pike were right: Do one thing, and do it well by ahofmann on Saturday August 19, 2023 @04:39AM (#37186779)
The article could have used the term technical debt. To me technical debt happens not only when new code gets added in a sloppy way, but also when the developer experience gets worse.
Re:Kernighan and Pike were right: Do one thing, and do it well by morelisp on Saturday August 19, 2023 @06:04AM (#37187188)
I really like Egon Elbre's definition of technical debt as idealized effort vs. actual effort to make changes - https://www.storj.io/blog/demystifying-technical-debt

It nicely captures a lot of the usually "fuzzier" things of technical debt, like how code even with no changes and no changing requirement somehow accrues technical debt (you get better, your idealized effort reduces).

Re:Kernighan and Pike were right: Do one thing, and do it well by SuchAnonMuchWow on Saturday August 19, 2023 @04:58AM (#37186871)
crushed by technical debt
Re:Kernighan and Pike were right: Do one thing, and do it well by sham1 on Saturday August 19, 2023 @11:46AM (#37189924)
Or "defaulting on technical debt".

That'd also play into the whole metaphor of technical debt.

Re:Kernighan and Pike were right: Do one thing, and do it well by oneshtein on Saturday August 19, 2023 @04:59AM (#37186880)
In my native language, we widely use therm "Information explosion".
Re:Kernighan and Pike were right: Do one thing, and do it well by asddubs on Saturday August 19, 2023 @05:50AM (#37187124)
if you're gonna go that way, you might as well go with shitfactoring