cross-posted from: https://programming.dev/post/23442993
Sometimes I create a solution to a simple problem. However instead of making use of the solution, I keep extending it unnecessarily. This is why for this kind of project, I want to systematically restrain my future self from adding new features beyond the initial vision e.g. by actively refusing generic and re-usable code.
What is the search engine friendly term for this approach or at least for this situation? “Ad-hoc programming” may be literally what I’m talking about, but in practice it’s associated with unplanned happenings.
Unfortunately, I don’t think anything like this really exists, because it violates good programming principles. Not to say you’re bad for considering it, but there probably aren’t a lot of people working toward the same end. You’ll probably have to resort to personal discipline and/or scathing code comments to remind yourself to refactor things before using them. I may or may not have left comments in my own code calling myself an idiot for not refactoring, or apologizing to my future self. Welcome to the club.