this post was submitted on 24 Jul 2026
431 points (99.5% liked)

Programmer Humor

32452 readers
1709 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 3 years ago
MODERATORS
anzo@programming.dev
Feyter@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
431
rm -rf /usr due to typo (sh.itjust.works)
submitted 1 day ago by testaccount789@sh.itjust.works to c/programmer_humor@programming.dev
46 comments fedilink hide all child comments
 

https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/issues/123

you are viewing a single comment's thread
view the rest of the comments
[–] bitjunkie@lemmy.world 41 points 23 hours ago* (last edited 23 hours ago) (2 children)

This entire thread is giving me flashbacks to my junior dev days and forgetting a where clause when updating/deleting database records

[–] EpicFailGuy@lemmy.world 26 points 20 hours ago (1 children)

ah! yes ... little bobby tables we call him.

[–] Buckshot@programming.dev 14 points 21 hours ago (1 children)

We've all done that at some point.

That sinking feeling when your quick update doesn't return immediately.

Good to get into the habit of wrapping your queries in a begin transaction/rollback until you verify the result 😁

[–] bitjunkie@lemmy.world 9 points 20 hours ago* (last edited 20 hours ago)

I was never able to fully form the habit with transactions. The guardrails I use are writing the where clause first and keeping my query tool in read-only mode for prod connections and only disabling it once I'm sure I need to make a change.