# Solving 200 Project Euler Problems

### Introduction

Last week, I achieved a goal of hitting 200 problems solved in Project Euler. If you are unfamiliar with Project Euler, it's a website where users can solve tricky problems that require both mathematics and programming to solve. An example question:

(BBBW) | (B,BBW) | (B,B,BW) | (B,B,B,W) |

(B,BB,W) | (BBB,W) | (BB,BW) |

**sixty**black objects B and

**forty**white objects W be thus grouped?

### What did I learn?

### Progress

I started in Jan. 2016, and was able to collect my progress of completion over time:

There is also the concept of the the "difficulty" of a problem, provided by the website itself as a measure of how often participants get the answer wrong. Here is the cumulative difficulty:

## Conclusion

I'm not finished with Project Euler yet - there are *way* to many problems I spent time on but didn't solve and they are just itching me. However, I am taking a break for a while so I can focus on some other projects. After all, solving 200 problems was *technically* my lifetime goal.

If a person asked me "is Project Euler worth the time?" - I wouldn't immediately say yes. You do need lots of time, and it really is a personal thing (there is a leaderboard, but it's not nearly as public as, say, StackOverflow's leaderboards). You also need to think about the opportunity cost - will solving these problems further your career or research? Personally, I feel that Project Euler rounded out my understanding of computer science and mathematics, and not so heavily loaded on statistics and Python applied to statistics.