You are viewing a single thread.
View all comments
101 points


oh god, it’s me

permalink
report
reply
83 points

Senior developer tip: squash the evidence.

permalink
report
parent
reply
26 points

Principle developer tip: rewrite history to make yourself seem smarter.

Soft reset the whole branch and commit a series of atomic and semantic patches (eg separating code, test, and refactor changes) that tell a clean narrative of the changeset to reviewers, future blamers.

permalink
report
parent
reply
3 points

And then my team squashes those commits 😩

permalink
report
parent
reply
2 points
Deleted by creator
permalink
report
parent
reply
2 points

Do you put effort into your commit messages before the rewrite, or just write something quick for yourself and then put in the effort later?

permalink
report
parent
reply
10 points

git commit --amend --no-edit

This helped me countless times…

permalink
report
parent
reply
6 points

Senior developer tip: Squash the evidence management

permalink
report
parent
reply
13 points

F

permalink
report
parent
reply
9 points
git reset head~9
git add -A
git commit -am 'Rebased lol'
git push -f
permalink
report
parent
reply
7 points

F

permalink
report
parent
reply
2 points

🫂

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

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

Community stats

  • 7K

    Monthly active users

  • 730

    Posts

  • 11K

    Comments