Oh sorry, I meant it the other way around!
So, I mean, I've seen this in scripts that I wrote to "quickly do some stuff".
1. Write the easiest possible implementation you can think of, just string together code in the REPL until it works, then put it all into a .py file
2. Some new need arises. Make the easiest possible change that causes it to work, like adding a new switch that completely changes the control flow.
3. Some new bug arises. Make the quickest possible change that causes it to work, like running the entire program in a while-true loop in case it crashes.
4. Continue along this manner until half of the code is commented-out garbage.
5. Rewrite.
There's no need to make it a thing of beauty, because it's easier to just scrap it and rewrite it. For the short term, making a "quick fix" is nearly always better, and for the long term, running a buggy piece of shit might still be preferable to spending good money to rewrite it.
(Also, the good stuff often already exists as open-source software, so it's only the hyper-specific stuff that's proprietary, and that will be closely tied to business needs.)
