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.

  • _cnt0
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    19 hours ago

    The unix philosophy is about making highly reusable and pluggable tools which is the exact opposite of what OP is asking for.