> APL is like a diamond. It has a beautiful crystal structure; all of its parts are related in a uniform and elegant way. But if you try to extend this structure in any way — even by adding another diamond — you get an ugly kludge. LISP, on the other hand, is like a ball of mud. You can add any amount of mud to it [...] and it still looks like a ball of mud!
Plus every now and then there's a reset where it all goes back to a tiny cohesive start before the chaos begins again.
Kind of the culmination of the "Big Ball of Mud" architecture, innit.
Screw you, I quit!
We could modify this to handle sysadmins too.
However, the political reality in any large company means shit will be shipped on a regular basis. This isn't unique to the dev/sysadmin roles. This happens in every area of business.
There's enormous glory to be had in visibly polishing turds - in mitigating well known, well communicated problems. Prevention is very important, yes, but it is not a panacea.
The description for Forth had 'ball of mud' in it. That bottom-up design where you start with a tiny core and keep adding little bits and smoothing them out then adding more over and over.
I always thought it was more like a snowball like in making a snowman sort of accumulation. But now... that final step when you have that last written that you give the command and the system removes all the bits that never get referenced from your application, squishes it down, polishes it up and spits out an executable.
Forth is very dorodango.
[1] https://www.joelonsoftware.com/2000/04/06/things-you-should-...
"I am prepared for the worst, but hope for the best." - Disraeli
Often we talk about the power of inertia in keeping around old codebases with terrible histories. We talk about how illogical it is that we don't throw things out and start anew. There's a hidden value in a known quantity which has had blemishes polished off. With a nod to mythbusters, even a turd can shine [1] given sufficient effort. We have all dealt with many turds in the course of our careers.
It is of course ideal to polish something more valuable than a turd. Architecture can still be rotten on the inside and necessitate replacement despite having a well polished exterior process. But new systems will always be unpolished no matter how well design. In the end there is no substitute for the smoothing process of constant handling.
[1] https://go.discovery.com/tv-shows/mythbusters/videos/polishi...