this post was submitted on 30 Jan 2026
762 points (97.2% liked)

Programmer Humor

29083 readers
1653 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 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
762
Senior devs... (suppo.fi)
submitted 3 days ago by cm0002@suppo.fi to c/programmer_humor@programming.dev
90 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] wpb@lemmy.world 2 points 2 days ago* (last edited 2 days ago) (1 children)

Quickest way to get a test suite so tightly coupled to structure rather than behavior that even just looking at the tests wrong makes them fail. But technically you do get test coverage I guess. Goodhart's law in action.

[โ€“] jjjalljs@ttrpg.network 1 points 1 day ago

It's not really that different from like


my_get_mock = Mock(side_effect=Some exception("oh no"))
result = some_func(http_getter=my_get_mock)

There's many ways of writing bad code and tests, but mocks and patches aren't always a bad tool. But sure, you can definitely fuck things up with them.