I'm in my third year of a computer science degree and recently received an opportunity to attend a convention with a respected US university. I'll be able to meet people, network, and hopefully make a strong impression, so I want to prepare well. The problem is that I feel lost despite being able to build reasonably complex programs. I don't want to graduate, get a job, and stop there—I want to create meaningful things and eventually push the boundaries of what's possible. I have plenty of ideas, but no clear plan for deciding what to pursue or how to start.
I often run into knowledge gaps when working on projects. For example, I wanted to build an economic simulation, but soon realized I needed much more mathematics and economics than expected. Projects that initially seem small can quickly become overwhelming. I also feel behind people who have active open-source portfolios and lots of public work.
I'm interested in Python, C++, data science, astronomy simulations, and several other areas. I'm worried that learning only what each project requires leaves holes in my fundamentals—for example, understanding a library without fully understanding the underlying language concepts. How can I choose a direction, strengthen my foundation, and gain practical experience without constantly feeling overwhelmed?
4 Answers
If a project requires knowledge you don’t have, that doesn’t necessarily mean the project is badly chosen. Learn the missing material. You may need to scale the first version down, but studying the relevant mathematics or economics is part of building the project. A project doesn’t have to be finished quickly to be worthwhile.
Open-source work can be a great bridge between coursework and professional development. Start with a project that genuinely interests you, build it locally, read its documentation, and look for small bug fixes, tests, or performance improvements. Large codebases feel confusing at first, even to capable programmers. Learning to navigate unfamiliar code is itself an important skill, so don’t treat that discomfort as proof that you know nothing.
It may help to separate three goals: learning fundamentals, building software, and exploring possible careers. You don’t need to solve all three with one enormous project. Work through a structured fundamentals resource, create smaller projects with clearly limited scope, and explore different fields through short experiments. For a simulation, begin with a deliberately simplified model and document its assumptions instead of trying to reproduce an entire academic field immediately.
Try not to spread yourself across every interesting subject at once. Programming is similar to learning a language: brief exposure to many areas gives you basic vocabulary, but sustained focus is what lets you have deeper conversations. Pick one main direction for a few months—perhaps Python data work or C++ systems programming—and use projects to reinforce the fundamentals as you go.
That makes sense. I’m especially concerned that learning things only when a project demands them leaves gaps in basic knowledge. I like Python and C++, but I may need to choose one as my main focus for a while instead of constantly switching between interests.