Joshua Simmons's Blog

Nobody likes making mistakes. Even worse is if our mistakes are on display for others to see. To have every little mistake we make recorded and published for all time is certainly not an ideal situation, but that’s often exactly what we do to ourselves when we put our work in version control systems like git!

How often have you had the unenviable choice between altering public history or making awkward revert commits?

How can we avoid such annoyances? Not use git? Perish the thought. One thing we can do is to fix our mistakes before we record them for posterity. We can even have git automatically stop us if we try to make a commit that contains a mistake.

How can such a miracle be possible, you ask? Read on to find out.

Strong go players extole the virtues of go problems as a key way to improve your skills, but rarely spell out exactly how to get the most out of your go problem study time. Having the wrong attitude or the wrong general method to solving problems will result in a frustrating and largely unrewarding experience. On the other hand, if you know the right approach you will get the most out of your study time and enjoy yourself too! Here I will present what I’ve learned to be the most effective ways to do go problems.