> The idea that just because your code solved the problem then it's good enough is bullshit, especially if you're not the one that has to maintain your monstros

> The idea that just because your code solved the problem then it's good enough is bullshit, especially if you're not the one that has to maintain your monstrosity of a codebase going forward. It's a lot better than beautiful code that _doesn't_ solve the problem. If I had to choose between them, I'd rather rewrite something that's wildly successful than try and make an unpopular piece of software popular. OP can learn how to write more maintainable software, but it sounds like they already have a good instinct for making useful software that people actually want. IMO that's rarer and more valuable.