Challenge: Solving 100 Short Go Problems
I’ve decided to start a personal challenge: to solve 100 short Go programming problems.
To do that, I will use Clash of Code from CodinGame.
These are short puzzle-like problems that users can solve using their preferred language.
Each problem takes 15 minutes or less, and you compete with other people.
My goal is not to compete, but to see how many of these 100 problems I can solve and how long it takes me to finish them all.
I’ll update this post once I’m done and report how many of these problems I was able to complete.
12/12/2025
And it’s done!
It has been fun and I completed more than I thought I would.
In the end it took me 15 days to complete the 100 problems (of course I did not work on them every day).
Out of these 100 puzzles I could not solve 6. I would say that was due to lack of time. I also partially solved 7. This means they passed some of the tests but not all. And finally 87 of them were completed flawlessly. I think it is a good result; also, I ranked first in some of these 87.
Considering that there are really good programmers there and also some cheaters and bots, my performance was pretty good.
One case worth mentioning is the last one. It was a bit complicated but I managed to solve 25% of the test cases. I considered it a failure but then I realized I took the first place because I was the only one who managed to solve something. It’s better to try and fail than not to try at all.
Another case was a Fibonacci-like puzzle where I also got first place. That’s because most of the players did not read the problem and just used the default Fibonacci formula (from Python 3) and sent the solution. But this was not what we were asked to do. We had to use the Fibonacci formula but with a slight modification. That is why they failed half of the test cases.
I would say I didn’t learn anything new, but I got more fluent in Go and got used to using the range statement more often instead of the classic for.