For those of you that follow me on Twitter(@MrFresh), youâ€™ve seen daily posts about my progress during this 100 Days of Code challenge. Iâ€™ve embarked on my third try at teaching myself how to code in Python. In short, the first was following tutorials on Codecademy, along with a book I bought, back in 2013. The second stint was trying an â€œIntroduction To Computational Programming Using Pythonâ€ course given by MIT, an online MITx course, commonly known as a MOOC (Massive Open Online Course). The first go around, I spent too much time just doing tutorial section after section. While that was ok, I wasnâ€™t really applying what I was learning. The MOOC was good, but there were so many global students involved with much more programming experience than me, that I kinda felt out of place, found myself spending too much time on the courseâ€™s Facebook page, resulting in it being difficult to meet the class assignment due date deadlines..
They say the â€œthird timeâ€™s a charmâ€. Iâ€™ve been putting in at least an hour everyday but this time around, Iâ€™m using the same book purchased years ago, â€œPython Crash Course â€“ A Handâ€™s On, Project Based Introduction To Programmingâ€â€¦ANDâ€¦building a project as as I learn. The latter is probably the most single important approach one can take when learning how to code. Picking something to build that you (or even someone others) can find useful, allows you to apply even the most minimal knowledge to something concrete. Iâ€™m seeing that this approach was the missing part in keeping me interested.
Here are a few other tips you may find useful:
- Donâ€™t try to learn everything at one time – find an approach that will allow you to become grounded in the basics, and move forward only when youâ€™re sure you have a grasp of them.
- Be mindful to avoid what I call â€œtutorial purgatoryâ€ – spending too much time watching tutorial after tutorial and not taking to write actual code. Try to write your own code similar to the exercises you follow, perhaps even modifying an exercise to add what youâ€™ve learned in other areas.
- Find a way to document what you learn, via writing it down in a journal or doing so online (Evernote, One Note, GitHub, etc)
- Put in some time studying and writing code everyday – consistent actions end up forming habs.
- Take advantage of anyway you can with the coding community available to you – often times those there are willing to help you.
- Again, continually write code, even the smallest, simplest programs, with comments in the proper style. Not only will it help you learn coding itself but get you familiar with the code editor and IDE you work in.
- Participate in the #100DaysOfCode challenge. Itâ€™s one that is beneficial to anyone just starting out through those with vast experience.
The challenge, in and of itself, is often helpful because there are many going through it, as well as just starting, that provide a vibrant, robust community of those willing to help and provide motivation. Iâ€™m exactly three weeks in and look forward to putting in the work everyday at this point (even knowing that theyâ€™ll be some hard days ahead).
I keep my progress posted on Twitter, as a note page in my Evernote account, and in a small blue notebook. At some point, when I feel that GitHub will be useful for me, Iâ€™ll create and maintain my log there, just as many do already. So far, my project is coming along nicely, itâ€™s nothing spectacular, but getting a glimpse of what I know Python can do, there will be lots of room for improving the code as I learn.
This is a cool journey you’re embarking on Brother. I’m not gonna front that’s over my head. Learning to code is a cool thing because it gives you insight on the how some programs work and it brings a smile to your face.
I enjoy your posts in regards to your “Wins” and “Challenges” on this project. You got this Bruh because when it comes to a challenge you stay the path. Keep us informed. 🙂
Thanks brotha, much appreciated!