this post was submitted on 07 Jul 2025

678 points (99.3% liked)

Programmer Humor

25059 readers

943 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

678

Production breaking driven developer (lemmy.ml)

submitted 1 week ago by HiddenLayer555@lemmy.ml to c/programmer_humor@programming.dev

39 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ChickenLadyLovesLife@lemmy.world 3 points 1 week ago (2 children)

capturing the rules as tests is a great way to make sure that rules remains true

Capturing the rules as documentation is also a great way to make sure that rules remain true.

Lol just kidding! Documentation ... can you imagine?

[–] Shanmugha@lemmy.world 3 points 1 week ago

Yeah, good luck reading 20+ pages of interlinked rules of what is what, what does what and in what order, then comparing that to how system behaves after your changes

Lol just kidding. No business rules are harder than five lines of text

[–] squaresinger@lemmy.world 1 points 1 week ago

Capturing the rules as documentation (especially external documentation like confluence) is a great way to make sure nobody ever reads it. Or even finds it.