I'm studying for an online software engineering degree while working, and I'm starting to feel overwhelmed. I've been learning Python with a beginner-friendly book and feel comfortable with the fundamentals. I'm now moving into the project section, but I'm wondering whether I should be using other resources or studying differently.
Would YouTube, Coursera, Udemy, interactive websites, or another book be more effective? I'm planning to learn SQL next and want to make good use of the next couple of years before graduating. I'd appreciate advice on how to study efficiently, what skills to prioritize, and how to balance structured learning with practical projects.
4 Answers
Don’t focus too much on finding the fastest possible route. Taking time to understand the fundamentals properly is usually more efficient than rushing and having to relearn everything later. Use your current book or course as your main structure, then experiment, ask questions, and revisit anything you don’t fully understand. A strong foundation will make future languages and tools much easier to learn.
Look for local or online technology events, hackathons, and study groups. Seeing what other developers are building can give you project ideas and expose you to problems beyond coursework. You could recreate a simple version of an interesting project, collaborate with other learners, and keep the process enjoyable. Consistent hands-on practice matters more than constantly switching between learning platforms.
I’ll try that. Working with other people and building something outside a tutorial sounds like a good way to stay motivated.
Build a regular practice routine around real projects, and supplement it with coding exercises. Platforms such as LeetCode or HackerRank can help you practice data structures, algorithms, and problem-solving, but they shouldn’t be your entire education. Real software usually involves designing, debugging, using libraries, working with data, and maintaining code, so projects are essential.
Try to move beyond following tutorials step by step. Tutorials are useful for learning concepts, but they can hide the difficult parts because the solution is already laid out. After finishing an example, change it or build something related without looking at the instructions. Even small additions create the useful friction that teaches you how to troubleshoot and apply ideas independently.
Even a minor change to a tutorial project can be valuable. If you can add a feature that wasn’t explained, it’s a good test of whether you actually understood the material.
That makes sense. I’m trying to learn the fundamentals thoroughly, but I’m also curious about which extra resources would pair well with my current book, especially for SQL.