4) git stash It lets you make different code changes to fix a bug without creating many local branches. You can save uncommitted changes in the stash and apply them later.

3) git blame It lets you find who and what caused the change. And helps you debug faster.

2) git add -i It lets you stage only the lines of code that you want. Also it allows you to squash and remove commits. Besides avoid "git add ." like the plague because you don't want to break the deployment with unwanted code.

1) git bisect It lets you do a binary search to find the commit that caused the bug. And helps you debug faster.

What would you add to this list? Also I write a weekly newsletter to teach system design. Try it with 30,001+ readers:

If you liked this thread. 🔔 Follow: @systemdesign42 ♻ Repost to help others find it. 💾 Bookmark it for future reference.

@systemdesign42 git bisect is a powerful one

@Franc0Fernand0 indeed

@systemdesign42 I have been using git for the last 7 years. Never even heard of git add -i. Tried it. I don’t know how I went this long without it. Thanks!

@SmithCommaDave oh, it's a handy tool.

@systemdesign42 @readwise save thread

@systemdesign42 +