this post was submitted on 04 May 2024
323 points (92.8% liked)

Programmer Humor

19694 readers
118 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
anzo
Feyter
BurningTurtle
pylapp
323
Added Bugs to Keep my job (sh.itjust.works)
submitted 6 months ago by [email protected] to c/programmer_humor
161 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 6 months ago (1 children)

lmaoo, I can't believe someone actually did that and was serious about it.
I'm already imagining commits piling up with comments like:

  • "add a newline"
  • "move function up"
  • "rename variable users to user_list"
  • "Revert previous commit"
  • "no John, it's user_list and that's it, don't you dare change it again"

He wasn’t an exec for very long.

Good riddance I guess

[–] [email protected] 5 points 6 months ago (1 children)

Oh, no, we can do better.

Every single line of every single PR is an individual commit. And never squash-commit.

[–] [email protected] 2 points 6 months ago (1 children)

Talk about atomic commits

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago) (1 children)

If you really want to nuke it from orbit: do it for every character.

It is absolutely technically feasible to go further than that, but I think that’s the point of diminishing returns in terms of effort.

[–] [email protected] 1 points 6 months ago

Hah, I knew it would come to that

but I think that’s the point of diminishing returns in terms of effort

Not if you make another application to automatically split commits in that way... application which will need its own commits, it's never-ending