if it ain't fixable, don't break it
this was such a single-brain-cell dashed off post but of course it's pithy and so it got some engagement. enjoy your personal interpretation of it as you like, but i'm not liking how it could be construed as a classic hostile elitist FOSS bro "are you cool enough to use this software?" saying. my sincere belief would be more something like, if people could come to depend on it, but it can break so as to be unfixable... don't build it in the first place!
if it's a piece of art that is designed to break / beautiful when broken, then that's fine, build it. and maybe the OP is a decent title for such a piece. free to a good home 😄
@jplebreton Software takes on a life of its own and you are doing a disservice to yourself and others by writing brittle code - for any purpose. Sometimes it's unavoidable but code like that should be deleted/archived/retired ASAP and not shared.
@jplebreton
if it ain't fixable, don't create it
@jplebreton But the replacement isn't ready yet (due in 20x6), and business needs to cram an extra feature in.
@jplebreton If it ain't fixable, figure out how to replace it before it blows up on your face.
@jplebreton "If you don't know how to fix it, please stop breaking it" was said in a historical speech by Severn Cullis-Suzuki, aged 12 years old in 1992. https://www.youtube.com/watch?v=oJJGuIZVfLM
Severn Cullis-Suzuki at Rio Summit 1992

YouTube
@jplebreton if it ain’t fixable, break it as a pretext for replacing it with something that is
@jplebreton as a late friend wrote in the READMEs for his free tools: “If it breaks in half, you own both pieces.”
@jplebreton nah, break it completely at the best possible time. Everyone gets to have a test system. Few are lucky enough to have a production system as well.