I'm a first-year computer science student, and this summer I focused on building a strong foundation. I learned Git and GitHub, practiced C from arrays through pointers, completed many exercises, and built a Tic-Tac-Toe game. I've also studied introductory data structures, recursion, sorting, and searching.
At university, I'll be taking Algorithms 3 and object-oriented programming with Java. I'm considering studying those topics more deeply while learning Python on the side, but I also see advice to start practical development early through areas such as backend or web development.
Would it be better to keep strengthening my fundamentals, start building projects in Python or another language, or begin exploring a specific area of software development? How would you balance coursework, algorithms, and practical experience at this stage?
3 Answers
Your foundation is already in a good place. Keep taking the Java, object-oriented programming, and algorithms coursework seriously, but also choose one practical direction—such as web, backend, or mobile development—and build a real project. You don’t need to master every prerequisite before starting; let the project reveal which concepts you need to learn next.
If your goal is eventually getting a software job, continue developing your fundamentals and practice data structures and algorithms, but spend some time discovering what kind of software work you actually enjoy. You don’t have to choose a permanent specialty right now. A few small projects in different areas can help you make that decision while your core skills keep improving.
Don’t treat fundamentals and projects as competing choices. A good split would be roughly half coursework and foundational study, and half increasingly ambitious projects. For example, a small client-server game or application with accounts and persistent data could make networking, databases, serialization, concurrency, security, and architecture feel much more concrete.
You also don’t need to learn Python simply because it’s the usual next language. Learn a language when a project gives you a reason to use it; going deeper with C and Java may be more valuable right now than collecting another syntax. As you use AI coding tools, treat them as accelerators rather than replacements for understanding. Ask why generated code uses a particular data structure, what its complexity is, how it works, and what could go wrong. You should still be able to explain and recreate the important parts yourself.
That combination of serious fundamentals and a challenging project seems more useful than choosing one or the other. I’ll try to use projects to expose the concepts I need to study instead of waiting until I feel fully prepared.
A useful rule for learning another language is to have a specific reason for it. For example, a functional language can teach a different way of thinking, while a systems language can deepen your understanding of memory safety. Practice solving familiar algorithm problems in a new language only when it supports a clear learning goal.
I’m confident I can finish the algorithms coursework, but I’m still unsure how to discover which part of software interests me. I’m thinking of combining the coursework with a practical skill or project rather than waiting until later to explore.