Why I Started Build First, Learn Later
Published on November 17, 2024
Why I’m Starting "Build First, Learn Later"
Hi, I’m Kennedy. I’m a computer science student, but if I’m honest, coding never really clicked for me outside of the classroom—until now. For years, I’ve followed the path of traditional computer science education: learning algorithms, solving coding exercises, and studying math-heavy concepts. While I value what I’ve learned, I always felt disconnected from it. I never felt inspired to take what I learned in class and apply it to my own ideas. It wasn’t until recently that I had an epiphany: I don’t love coding for the sake of coding. But I do love the idea of using code to build things that can help people. That realization changed everything. I’ve decided to stop waiting for the “perfect time” to start creating and instead dive into learning by building real, meaningful projects. This blog is my way of documenting that journey.
My Background in Coding (And Why It Didn’t Inspire Me Before)
As a CS student, I’ve had exposure to languages like Java, Python, and C++. I’ve studied the foundations—data structures, algorithms, and computational theory—but those topics often felt too abstract to inspire me. Outside of homework assignments, I rarely felt the drive to create anything.Languages like HTML, CSS, and JavaScript aren’t completely foreign to me, but I’ve never taken the time to truly explore their potential. My skills are far from expert level, but I’ve realized that I don’t need to be an expert to start creating. I just need to start.Why "Build First, Learn Later"?
I realized that what excites me most about coding isn’t the code itself—it’s what I can create with it. Whether it’s a simple tool that makes someone’s life easier or a fun app that brings a little joy, coding is a means to an end. It’s a tool for solving problems and building things that matter. That’s the philosophy behind "Build First, Learn Later":- Start With an Idea: Find a problem I care about or an idea I want to explore.
- Build a Basic Version: Create a simple, functional solution without worrying about perfection.
- Learn Along the Way: Pick up the skills I need as challenges arise.
- Iterate and Improve: Make things better as I go, using feedback and lessons learned.
What This Blog Is About
This blog is my way of documenting my journey and sharing what I learn along the way. Whether you’re a CS student like me or someone just starting out, I hope it inspires you to pick up an idea and start building.Here’s what you can expect:
- Project Tutorials: I’ll walk you through the tools and apps I create step by step.
- Lessons From the Process: I’ll share what I struggle with and how I solve those challenges.
- Reflections on Learning: Posts about why I believe in learning by building and how it’s transforming the way I see coding.
What’s Next?
My first project will be a Mood Tracker—a simple app where users can log and visualize their daily emotions. It’s a small but meaningful idea, and I’m excited to see how it takes shape. Once it’s ready, I’ll share the process, the code, and everything I learn along the way.Why This Matters to Me (And Maybe to You, Too)
If you’ve ever felt uninspired by traditional coding education or unsure where to start with building your own projects, you’re not alone. For the longest time, I didn’t feel confident enough to create outside of the classroom. But I’ve realized that confidence comes from action—not from waiting to feel ready.This blog is my starting point. I hope it can be yours, too.