I'm 19 and want to get back into programming, especially because I'll be studying an informatics-related major. I first experimented with HTML, CSS, and JavaScript around age 14, but never progressed very far. Later, I made a small game in C# by following tutorials, then stopped because I assumed programming might not be for me. Over the past few years I've struggled with distractions and low motivation, and I'd like to build something more productive and useful for my future. How should I choose a language or area to start with, figure out what I actually enjoy, and eventually prepare for a career in the industry? I also have trouble finishing video courses—I usually quit after one or two weeks—so advice on learning consistently and avoiding tutorial burnout would be especially helpful.
5 Answers
For a structured start, try a beginner-friendly Python course such as Stanford’s Code in Place. After that, a foundations-focused web curriculum can help you practice by building projects. Introductory computer science lectures are also useful when you want conceptual understanding, but don’t let collecting courses replace writing code. Set a small weekly goal and finish projects instead of jumping between tutorials.
There isn’t one universally best language. Pick a small project or area that seems useful to you, learn the language needed for it, and see how you feel after actually building something. Once you understand fundamentals like control flow, data structures, and memory, learning additional languages becomes much easier. Your first choice matters less than practicing consistently.
It’s possible that programming simply isn’t the right interest for you, and that’s okay. However, quitting tutorials doesn’t necessarily prove that. Try a short, project-based experiment instead: spend two or three weeks building something tiny without aiming to master an entire language. If solving and debugging those problems still feels completely uninteresting, explore other fields rather than forcing yourself into coding.
Look at the entry-level jobs, internships, and courses available where you live, then use those to build a roadmap. A language is only part of the picture; fundamentals such as data structures and algorithms, databases, version control, testing, and eventually systems or cloud concepts are also important. Don’t try to learn everything immediately—choose a direction and build several projects that demonstrate progress.
If you want something hands-on, an inexpensive microcontroller starter kit can make programming feel more concrete. You can use C or simple C++ to control sensors and LEDs, which gives you immediate feedback and creates lots of small project ideas. Alternatively, continue with C# and make another small game—but this time change or expand the tutorial project so you’re solving problems yourself.
C is valuable for understanding low-level concepts, but you don’t need to start there unless systems programming interests you. A safer or more modern language may be more practical for some career paths, so choose based on the kind of software you want to build.