this post was submitted on 12 Apr 2024
795 points (98.8% liked)

Programmer Humor

19551 readers
1023 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
795
We'll refactor this next year anyways (programming.dev)
submitted 7 months ago by popcar2@programming.dev to c/programmer_humor@programming.dev
51 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] magic_lobster_party@kbin.run 7 points 7 months ago* (last edited 7 months ago)

You can build your systems with as few assumptions as possible. The fewer assumptions you make, the less probable it is that any of your future assumptions will conflict with your previous assumptions. Your code will be built for change.

If your API call to some external system assumes the existence of a particular button in the UI, then your system isn’t built for change. Maybe you want to change this button? Then you need to go through all places in the code that relies on this particular button to see if it doesn’t conflict with any of their assumptions.