A week ago I decided to tackle the 100 Days of Code challenge. I’ve now completed day 7.
- I’ll code for at least 1 hour per day for 100 days.
- I’ll include time spent doing some tutorials, as well as working on projects, because I want a structured way to learn some fundamentals. Good tutes will make me faster. Whooshh.
- I’ll post my daily log to Instagram and upload what I’ve done to GitHub.
My Goals, by the 100th day
- Be familiar with using arrays, pointers, references, and basic object-oriented programming to create interactive designs and games using C++.
- Complete the code for some projects: Wiggin Out (a reflection on parenting) and Sun Defender (an arcade machine).
- Complete up to Chapter 9 or learncpp.com (I’m up to Chapter 4.6).
- Complete Udemy’s Learning Path: C++ Game Programming (It’s the only clear explanation of how to structure a program using OOP that I’ve been able to find. I’m 30% through it and it’s great!).
- Focus on C++ programming language because I have been dabbling with it for two years. And it seems to be relevant to several areas including arduino, Unreal game engine and software development using XCode IDE.
What is the 100 Days of Code and Why?
The 100 Days of Code was initiated by Alexander Kallaway in 2016, as a personal challenge and invitation to others to join him. By the end of 2017, around 3,000 people had tackled the challenge. He conceived the challenge as a way to help himself direct more energy and attention to learning and becoming a better programmer, rather than becoming a better Netflix consumer.
I decided to take on the challenge because I enjoy making interactive things, and have many ideas for more. But programming is a major bottleneck, often a deep quaggy quagmire, to progressing ideas and producing work. I want to get quicker at getting out of the quag, or even avoid it all together (but I doubt that’s possible).
I also really enjoy programming and am finding it requires a lot more creativity than I thought it did.
Header image: Artax