425
Coomitter be like (lemm.ee)
submitted 2 years ago by to c/programmer_humor@programming.dev
44 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 86 points 2 years ago (8 children)

Senior developer tip: squash the evidence.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 28 points 2 years ago (5 children)

    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
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    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
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 years ago

    Depends, but usually I will put in the effort up front and maybe tweak them in an in[eractive rebase, or just manually copy+paste.

    If they're worth saving. Sometimes you have to kill your darlings though

  • permalink
  • fedilink
  • source
  • parent