Short and to the point
100 Days of Coding Problems is a blog that I made to document my solutions and thinking to various coding problems.
To learn more about why I started it, continue reading below.
A few weeks ago I realized that, as I am still a student, I do not have very many coding projects at my disposal to present to various companies that I want to intern at. I was doing coding problems in school—and for fun—fairly regularly, but each one was quickly forgotten or deleted (because, like, what am I supposed to do with thirty coding problems lying around).
I decided that, since I was already completing coding problems fairly regularly and I needed something to show to companies in the form of my coding experience, I would create this blog known as 100 Days of Coding Problems.
I start each post with a background cover that relates to the problem at hand—maybe a skyscraper for building problems, or a plant for tree based problems—and then describe each problem exactly as it was found with the necessary attribution at the bottom.
I document my solution with the code in the necessary language, as well as putting a link to view the code for the sake of testing or playing around with. In addition, I try to provide an explanation as to the steps of solving the problem or maybe even my thought process about the problem itself.
If this sounds at all worth reading, I welcome you to glance around at some of my sample solutions and, if you’re daring, sign up to get my new posts emailed to you by entering your email in the top right of this page (very bottom if you are on mobile).
Although the name 100 Days of Coding Problems suggests that posts will be created daily, that is not the case. As much as I would like to post a new problem and solution everyday, my schedule is currently strict enough as to not allow it. I will try to keep up with posts fairly regularly 2-5 days apart, but no guarantees as of right now.
I also don’t think it makes sense to post a new problem and solution daily as, if you are following by email, that would be a pretty annoying daily email to receive in my opinion.
As I am a very big fan of self-improvement, do not hesitate to comment on my solutions if you think that there is a better way of doing it. That being said, I respond best to constructive criticism instead of negativity. If I agree with your feedback, I’ll update the solution accordingly (or try to get more information in the comments if I disagree) and, of course, give credit where credit is due.
Alternatively, if you would rather not leave a comment, feel free to shoot me an email at email@example.com and I’ll get back to you as soon as possible.
Since then, I have worked on numerous personal and professional projects. Before my first computer science class in school, I already had twelve web apps under my belt. I have competed on two competitive robotics teams, and am now taking a second computer science class in functional programming and chip design. You can read more and view some of my projects on my website.
I respond best to email, but you can also find me on: