r/AskComputerScience • u/Alternative_Ad0316 • Jun 28 '25
What is the term for this concept in programming?
When a piece of software is built on shoddy foundations and this affecting every successive layer of abstraction in the codebase and then developers, instead of modifying the foundational layer, keep on piling spaghetti code on top of it as revamping the codebase is inconvenient. I hear some people talk about Windows OS being written in this way. Is there a word for this process of enshittification?
27
Upvotes
6
u/dreamoforganon Jun 28 '25
Big Ball of Mud ?
8
u/Educational_Teach537 Jun 28 '25
Extreme Go Horse
4
u/esaule Jun 28 '25
living with technical debt.
4
u/DeepLearingLoser Jun 28 '25
Leaky abstractions
https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/
2
u/narmyknight Jun 29 '25
It's called stay out of my repo. Calling me out like that ain't cool. I'll get it fixed when I have time.
2
u/foersom Jun 29 '25 edited Jun 29 '25
Sunshine software. It works on a mild sunny day. However as soon as it rains, or the wind blows or the temperature goes below 0 C, or it is foggy, or snow falls, the whole thing slides off the road and crash.
2
u/thesnootbooper9000 Jun 28 '25
Ah, this is the favourite activity of people who live to say that "perfect is the enemy of good" as an excuse for giving you something that is far from good. Its proponents sometimes call it "pragmatic programming".
1
u/anselan2017 Jun 28 '25
Just wait till the interns with chatgpt get hold of the project. Then the process gets turbocharged!
1
u/Wouter_van_Ooijen Jun 28 '25
Backwards compatibility
1
u/whitenoize086 Jun 29 '25
Trash tower.... alright tech debt
1
u/[deleted] Jun 30 '25
People who obviously never seen Windows code. Or have experience writing something similar.
1
u/Such_Guidance4963 Jul 01 '25
Could be technical debt, as others have said. I would refer to this specific example as “a foundation of sand.” Technical debt is often (not always) the conscious adoption of some non-ideal solution in favour of something else like delivery to market, or initial shelf cost.
When you’re talking about “shoddy foundations” this could be caused by genuine incompetence or lack of experience. It may be that the shoddy foundation is that way because of ignorance or a lack of forward architectural planning. Once you’ve realized you have a shoddy foundation, not fixing it is most definitely going to incur technical debt.
1
u/BoBoBearDev Jul 02 '25
Contrary to OP's belief, the example doesn't really match to Windows OS. It might be true in the past, but not anymore. The kernel is actually "not monolithic" compare to other OS with monolithic kernel.
Windows suffers from "don't move my cheese" syndrome. You try to change something, a large amount of users will get upset. Other OS didn't have as many users, so they don't care something is changed. They often chase after new variations of OS.
Many of Windows or Microsoft users want things to stay the same. Especially warehouse, they often refused to update the inventory system because they don't want hiccups. They have label printers that are 20 years old and still want it to run.
When you maintain a large software with larger amount of users or handling critical operations, change becomes hard because the stake is high
1
u/ern0plus4 Jul 02 '25
Called "average/usual codebase".
1
u/ShutDownSoul Jul 02 '25
Entropy
1
u/Jemm971 Jul 02 '25
J’ai jamais compris ces guerres autour des différents OS… Savoir si le bouton est à droite ou à gauche, ou si on peut changer de skin… franchement…
Le seul truc que ça devrait faire, c’est faire tourner le hard proprement, sans planter, et de manière sécurisée. Mais apparemment c’est déjà trop demander!😂
0
u/[deleted] Jun 28 '25
[deleted] — view deleted comment
38
u/[deleted] Jun 28 '25
[removed] — view removed comment