When you get into Computer Science, or any tech career really, you face a decision:
You can dive into projects, exploring new languages and technologies in a whirlwind of experimentation. Or, you can take a more methodical path, building your skills step-by-step to lay a solid career foundation.
I chose the first path—jumping into projects and learning by doing. While this can be exciting and full of potential, it comes with its challenges: unfinished projects, moments of self-doubt, and that nagging sense of whether you've lost sight of the goal in a fast-paced industry. Many times, it feels like you've missed the train, as what was once an exciting vision, transforms into a mound of wasted time.
If this sounds familiar, here are some strategies to help you stay productive and maintain momentum:
Keep track of what you build, whether it’s successful or not. Documentation not only helps others understand your thought process, but it also serves as a guide for you to revisit ideas later. Use tools like GitHub, Notion, or a simple markdown file. Good documentation transforms half-baked projects into valuable learning experiences.
Share your progress and challenges openly. Platforms like Twitter, LinkedIn, or even a personal blog are great for this. Building in public creates accountability, invites feedback, and may connect you with collaborators or mentors who can help you improve. There's a good chance that someone else had tried what you're building before & most of the time, they are willing to share their experiences. This can open doors to conversations on market assumptions, hidden challenges, gold tips & so on.
Lets address the elephant in the room & I am not talking about your girlfriend. You're probably excited about your idea because you feel that its unique & you've got an unfair advantage with your novel perspective. Sharing your work may open doors to copy cats and thieves,. If that's the case with you, strike a balance of how much you're sharing, weigh it against the benefits of feedback & having a warm userbase for testing and launch, then make a wise decision. Unless your making military weapons or something, I think you'll be fine building in public.
Anyways, when in doubt, ask a trusted adult, your mentor
Don’t just code in isolation—share what you’re working on. Explaining your projects to others, whether you're writing articles about it, posting on Linkedin, or even conversations,sharing helps to clarify your understanding and exposes assumptions and plot holes. It can also attract like-minded individuals who might be interested in collaborating. Like me. Feel free to contact me
A good wife comes from the Lord, and when you're patnering with someone on a worthwhile venture, it's like a marriage. If you’re working with a team and it’s not functioning well—whether it's due to lack of communication, commitment, or alignment—don’t hesitate to make tough decisions. A dysfunctional team can slow down progress and drain motivation. Prioritize healthy collaboration.
It’s tempting to bypass the basics when you’re excited about new technologies, but understanding core concepts will speed up your development in the long run. Balance project work with learning fundamentals to build a stronger foundation—think of it as sharpening your tools as you go.
Many ambitious projects fall by the wayside because they feel too complex, uninteresting, or "not viable" anymore. If an idea doesn’t work out, don’t just abandon it. Archive it, document what you learned, and add it to your portfolio. Even incomplete projects can showcase skills and creativity.
A portfolio is your personal showcase—proof that you’ve been busy creating, experimenting, and learning. It doesn’t have to be perfect, but it should highlight your strengths and interests. A portfolio makes your journey visible to potential employers, clients, or collaborators.
As you grow, your skills improve. Don’t shy away from revisiting old projects. You’ll have new perspectives, better tools, and more experience. Sometimes, breathing new life into an old idea is easier than starting something new from scratch.
There will be times when your projects lose their initial excitement. Stick with them, even when they feel like a grind. Building something great often requires pushing through the mundane parts. Embrace the challenge—success is about persistence, not perfection.
You've probably heard that 99% of gamblers quit right before they win big, but seriously though, you don’t have to go down with your ship. Sometimes, a project isn’t going anywhere, and it’s crucial to be honest with yourself when that’s the case. If you hit a wall, find a way around or over it, or move on to the next idea. But don't forget to put it on your portfolio anyway, as we discussed earlier. There's no real failure here, it's just the scenic route to your ultimate success.
Choosing the builder’s path in Computer Science means embracing the uncertainties and occasional failures that come with it. It’s not always the fastest or easiest route, but it’s a fulfilling one.By documenting your journey, sharing your progress, and staying committed to your projects, you can carve out a unique space for yourself in this fast-moving field. This is a path reserved for the brave, congratulations. I can't wait to witness your big break.
Thanks for reading!