Re:Code Is Clay Now
by AnthonyMouse on Thursday October 22, 2026 @03:41AM
(#50192399)
It would be great if we could have exact opposite of this.
The problem with most existing code is that you start off with the MVP, which is terrible because it needed to get out the door by the deadline. At which point tons of people start using it and you're stuck supporting the poorly conceived original interface for decades because so many things now depend on it, while also trying to support three newer versions because those versions had their own deadlines and now people are expecting them to continue working.
If we could realize the promise of these things then ideally what would happen is that the efficiency would make it cost effective to make the "MVP" a good well-tested well-considered final product. At which point it's done and has minimal if any future changes because you got it right the first time. Which is very useful to the human users who then don't have to re-learn how the thing works every 18 months.
The problem with most existing code is that you start off with the MVP, which is terrible because it needed to get out the door by the deadline. At which point tons of people start using it and you're stuck supporting the poorly conceived original interface for decades because so many things now depend on it, while also trying to support three newer versions because those versions had their own deadlines and now people are expecting them to continue working.
If we could realize the promise of these things then ideally what would happen is that the efficiency would make it cost effective to make the "MVP" a good well-tested well-considered final product. At which point it's done and has minimal if any future changes because you got it right the first time. Which is very useful to the human users who then don't have to re-learn how the thing works every 18 months.