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.
Sounds like the unix philosophy of small tools that do one thing and can be plugged together via pipes.
Make a well designed public interface and make the classes
final.The unix philosophy is about making highly reusable and pluggable tools which is the exact opposite of what OP is asking for.