I love solving programming contest problems! They are in a sense puzzles that require you to use programming, logic, and mathematics to solve them. Like all good puzzles they are designed to be both difficult and fun.
I've solved over 1350 problems on Kattis which as of November 2021 puts me in 13:th place globally. On Codeforces I have an Elo rating of 1961 putting me in the top 10% of users. Finally, I've recently started solving problems at Project Euler where I have 75 solved problems putting me in the top 3% of users. Of those Kattis is my platform of choice as it has a wide range of high quality problems that you can solve at your own pace.
One issue I have with most programming contest problems is that you either pass or fail. The issue with pass or fail is that there's no reward for trying or improving. Google Hash Code doesn't pass or fail solutions. Instead you get one, very hard, problem and have to give it your best shot which I love! With the help of fantastic friends I've placed in the top 7% in Google Hash Code.
What does this all mean? It means I have a passion for problem solving and that I'm able to quickly identify and implement solutions for algorithmic programming problems.
Games are really fun. They are fun to play, think about, and make. That is probably why I've been making prototypes for small games my whole life.
Currently I'm working on one game. It is a cart racing game with a twist: the cars can only drive in the four cardinal directions. This makes for an experience that is simple to pick up but incredibly hard to master. I'm hoping to have more to show soon!
As mentioned I've developed plenty of smaller games over the years. To see a sample of what I can do, please check out my showcase page!
Programming small games and solving programming puzzles have something in common. There's no need to invest a lot of time into a single problem. You don't have to spend time polishing code or focus on writing clean code. That is why I'm happy to have worked with larger code bases!
I've been employed as a software developer at Ericsson. It is through work I've learnt how and, more importantly, why to write clean code. Through work I've learnt to work with large code bases and how to effectively analyse code at large and long term projects.
