Background:
A few years ago myself and another programmer got hooked on the Python Challenge. This is a programming challenge designed to be solved in Python which asks the programmer to decipher and solve a range of small but increasingly difficult puzzles in a variety of problem domains. From the source files I've had kicking around since then it looks like I managed to get to challenge 17 before either giving up or getting distracted with something else. I did this mainly as an excuse to learn Python and had a great time doing so. So much so that I was able to start building tools in it and now consider it the language I feel most comfortable with after C#.I've been reading about the Go programming language for the last year or so but haven't really had the chance to learn or use it in anger. I thought that attempting to solve as much of the Python challenge using it as i could would be a decent learning experience. If it worked for Python, why wouldn't it work for go?
Goals:
1. Learn Go to a reasonable standard.2. Get comfortable using Git and Github.
3. As with everything I try and do, to become a better programmer.
Rules:
1. All challenges will be solved in only Go.2. I will resist, as much as possible, from looking up the answers to challenges and looking up the answers to challenges in the source files I had from when I first attempted the challenge using Python.
3. The source files for all challenges will be published on GitHub for posterity. I'll endevour to write about what I've learnt about Go after publishing and talk about what problems I had in their implementation.
