Why I Choose to Teach Myself Computer Science

A few years ago, at my last employer, I was troubleshooting a network issue at work when it hit me—I didn’t just want to fix tech problems. I wanted to build tech products and contribute to real innovation. That moment kicked off a journey that led me here: teaching myself computer science without a traditional CS degree, but a concept, projects, and late-night debug session at a time.

*Starting From the Ground Floor*

My career in tech didn’t begin in a classroom—it started in the field. Since 2009, I’ve worked in IT support, systems administration, and now in project management roles. Over the years, I developed a strong understanding of infrastructure and business needs. However, I have a desire to bring innovative impact to society, or even an organization. Unfortunately, such roles, require a background in computer science, not IT. Therefore, I am supplementing my graduate degree in Technology Management and Leadership, which includes Computer Science courses, with a more complete foundational layer in Computer Science.

Despite earning a management degree and now pursuing a master’s in Technology Management & Leadership, I realized that to truly evolve in the direction I wanted—toward technical leadership or product development—I needed to deepen my technical knowledge, particularly in computer science.

*Why I Skipped the Traditional CS Degree*

There are a few reasons I chose to go the self-taught route:

- Career Outlook: I do not wish to be a developer or programmer but a person who understands and facilitates technical teams.

- Flexibility: I’m balancing work, grad school, and a marriage. A full-time (or even part-time) CS degree just didn’t fit in my life.

- Budget: In addition, at this point I will have to sell illegal substsance to pay-off these school loans.

- Experience Over Theory: I’ve already been working in tech for over a decade. I didn’t want to start over—I wanted to level up with purpose.

- Access to Resources: Today’s online platforms (like MIT OCW, Udemy, EDx, Coursera, YouTube and more) offer more access to quality education than ever before—often for free or considerably low price. In addition, I can audit a course from my univeristy.

- Personal Drive: I believe learning is about persistence, not pedigree (although, it does matter). If I could manage enterprise infrastructure and lead complex IT projects, I could teach myself the deeper stuff too.

Of course, this route is not easy. I am sure I will have to navigate a lot of noise out there, and imposter syndrome creeps in sometimes. But every breakthrough—no matter how small—reminds me that this path is valid.

*What’s Next*

This blog is both a personal log and a public resource. I’ll be sharing:

- Real reflections from a self-taught learner

- Learning resources I actually use and recommend

- Project breakdowns and lessons learned

*Thoughts on tech, leadership, and building a fulfilling career*

Eventually, I want to transition into a Technical Program Manager or product-oriented role that blends my business insight with technical depth—and maybe inspire others who are self-taught or career-switching along the way.

*Let’s Learn Together*

If you’re on a similar path—or even just thinking about starting—welcome. I’m not here as an expert, but as someone who's committed to learning in public. Feel free to follow along, share your story, or drop a comment. Let’s build the future, one line of code at a time.