I have always wanted to code. Actually, I have always been interested in learning about computers, my desire to learn code arrived much later. As a student, I had a friend who was studying computer tech, and whenever I had a problem with my computer (be it a software update, hardware issue, etc.), I would watch him work on it, take mental notes, and the next time something similar occurred, I would try to fix it myself. I was so intrigued about all things tech and computers back then that whenever I heard words like “program," "developer," "internet," "code," etc., I felt inquisitive and wanted to know more about them. However, as an accounting professional with a hectic work schedule, I had no time to indulge my curiosity about an industry I was passionate about. Additionally, due to my lack of background in STEM, I thought there was no way I could break into tech. Then came the pandemic, and the lockdown left me with extra time on my hands. So I started reading online, and I discovered that and (like me) had no formal background in tech. This motivated me greatly, and I realized that maybe there is hope for me after all. So I started researching how to learn to code. While doing that, I heard about , and coincidentally ran into on Discord. It was amazing that I stumbled upon that post when I did because before then, I had never heard of Discord, and not long after joining, I learned about the free Python course. lots of developers are self-taught freeCodeCamp this article about a virtual meetup for developers to learn together Stanford Code in Place It was during the application process for this online class that I first discovered what programming was all about. I don't know if anybody else remembers their first time learning code, but mine was so exciting, I decided to . I promised myself I would pick up other learning resources at the end of the class to continue my coding journey, but that was not to be. blog about it Before enrolling in the course, I created an account on The Odin Project and , where I started taking basic HTML lessons. However, I took a break once the Python class began to concentrate on the course fully. As I mentioned earlier, I wanted to continue studying web development after the class. However, between my still-exhausting full time work schedule and other life dynamics, I never went back to coding. I signed up for courses on through the 2020 program but later dropped out because I selected the wrong learning track. My freecodecamp and The Odin Project courses were waiting for me, but I kept pushing back my start date until there were no more days left in 2020, and I realized I had not actually done any coding at all. Code-in-Place freeCodeCamp PluralSight Google Africa Developer Scholarship On my list of resolutions for this year, learning to code was at the top. However, when the first half of 2021 came and left, I realized I hadn't managed to do as much coding or learning as I really wanted. Other commitments and hindrances kept cropping up - there was always something else I had to do. But I was determined to learn how to code. Each time I receive a newsletter from a developer community (like Hashnode, , or ) I've subscribed to, I'm reminded all over again how much I'd like to be a part of this. Devto Quora code groups As the second half of 2021 approached, I realized that another year was drawing to a close without me accomplishing my dream. Naturally, I didn't want that so I decided to make a new plan to commit to learning to code for at least one hour every day. Since mid-July, I've been trying out this new plan; I finally logged into my account again for the first time since leaving it last year. However, because I tend to procrastinate and not finish things, I'll be employing a to by blogging on what I've learned each week. The Odin Project commitment device learn in public To this end, I have created a series on Hashnode titled , in which I will be documenting what I learn each week. Since July, I have already drafted five posts on what I've learned; however, I wanted to post this article first before publishing them. Having done so now, I'll be publishing every week. 🤞 I know that this will not be easy, distractions will probably arise as usual, and other commitments (work, life, etc.) will require my time, but I intend to see this through. #mytechjourney Hey, thanks for reading!