this post was submitted on 28 Dec 2024
11 points (66.7% liked)

Programming

17752 readers
1027 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
11
Terms for intentional anti-extensibility (self.programming)
submitted 1 week ago by TheV2 to c/programming
20 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Feyd 1 points 1 week ago

I would recommend just trying to cultivate a YAGNI mindset. I add a little more to the rationale - we are not very good at accurately predicting future requirements so rework/unraveling work becomes likely.

Following from there, trying to use technology (I could be misinterpreting but I think that's what you mean by "systematically restrain") is also going to be things you don't need.