This is probably the question I get asked the most when people find out I code. And every time, I give the same annoying answer.
It depends on what you want to build.
I know that sounds like a dodge, but hear me out. Today I’m comfortable using 14 programming languages when I need them: C++, Python, C, JavaScript, TypeScript, SQL, Bash, PowerShell, CUDA, HLSL, MEL, C#, Swift, and R. Add in frameworks like React and Angular, and the list gets even longer. That looks impressive, but I didn’t sit down one day and decide to learn all of them. Not even close.
I learned every single one because I was trying to make something.
When I needed to store and organize data, I learned SQL. When I wanted to automate boring tasks and work through complicated calculations, I picked up Python. Running heavy calculations on a GPU meant CUDA. And at work, managing systems meant getting comfortable with Bash and PowerShell.
The creative side pulled me in other directions. When I got into Unreal Engine and wanted to write my own shaders and push performance, that meant C++ and HLSL. When I started animating and rigging characters in Maya, I needed MEL to script the tools I wanted. Unity pulled me into C#. Wanting to build web interfaces led me to JavaScript, then TypeScript, and eventually frameworks like React and Angular. Wanting to mess around with iPhone apps meant Swift.
None of it happened in order, and none of it started with a course. Every language showed up because a project needed it.
Even the languages I already knew kept growing for the same reason. Python is a good example. I’d been using it for years to automate things, but when I started my master’s in cybersecurity, I had to use it in a completely different way. Suddenly I was writing scripts to dig through logs, analyze network traffic, and understand how attacks actually work. Python is one of the most widely used languages in security, and my coursework pushed me to use it more carefully and more often than I ever had. My skills got sharper, not because I set out to “get better at Python,” but because the work demanded it.
That’s the part I wish someone had told me earlier. People spend weeks researching the “best” first language, watching comparison videos and reading forum arguments, and never actually write anything. The language matters a lot less than having a reason to use it.
Once you learn your first one properly, the second comes faster. By the fifth or sixth, you start noticing that most languages share the same core ideas. Variables, loops, conditions, functions, data structures. The syntax changes, but the thinking stays the same. Picking up a new language stops feeling like starting over and starts feeling like learning a new accent.
So here’s my honest advice.
Figure out what you want to make first. Then pick the language that gets you there.
- Want to build websites? Start with JavaScript.
- Want to work with data or automate things? Start with Python.
- Interested in cybersecurity? Python again, then Bash and PowerShell.
- Want to make games? Look at C# for Unity or C++ for Unreal.
- Want to build iPhone apps? Swift.
- Not sure yet? Python. It’s readable, forgiving, and useful almost everywhere.
Then build something. One of the best ways to start is by cloning something you already use. Try making your own simple version of a to-do app, a weather app, a calculator, or even a basic Twitter or Spotify layout. You already know how it’s supposed to look and work, so you can focus on figuring out how to make it happen instead of deciding what to build. It will be messy, and it won’t be as good as the real thing. That’s fine. You’ll learn more from one finished clone than from ten tutorials.
Courses can help too, as long as you’re building alongside them. When I want to sharpen a skill or fill in gaps in my understanding, Udemy and Coursera have been two of my go-to places. On Udemy, I’d recommend 100 Days of Code™: The Complete Python Pro Bootcamp by Dr. Angela Yu, which has you build a new project every day, and Beginning C++ Programming: From Beginner to Beyond by Dr. Frank Mitropoulos, which does a great job explaining the fundamentals. If you want something more structured, Coursera’s Python for Everybody from the University of Michigan and the Google Cybersecurity Professional Certificate are great places to start, especially if a certificate would help your resume. Those are just a few of many. The trick is to use a course as a guide, not a substitute for building your own stuff. Watch a lesson, then go make something with it.
I didn’t get comfortable with all these languages by studying them one by one. I got there by building things I cared about and learning whatever they required along the way.
So stop asking which language to start with. Ask what you want to build. The language will follow.
