JavaScript, Java, Python … who cares. 🤷🏻‍♂️

This is a summary of a video I published on YouTube. You can click on the link below to watch the full video.

Stop Building Your Career Around Languages

One of the biggest mistakes I see developers make is tying their identity to a programming language. JavaScript, Python, Java—it feels important early on, but it’s a trap. Over a long enough timeline, you will switch languages multiple times. I’ve used around nine in real commercial projects, and none of them defined my career.

Languages matter for a specific job, not for your long-term direction. If you anchor your thinking to syntax, you end up constantly resetting your confidence every time you switch stacks. That’s wasted energy.

Tutorials Are Not Development

Another common issue: people stay in tutorial mode far too long. One or two tutorials are fine, but after that, you need to build real things. That’s where the learning actually happens.

Watching tutorials is like hitting a heavy bag. It feels productive, but it doesn’t prepare you for a real fight. Real development means dealing with messy requirements, unclear problems, and code that doesn’t behave nicely.

If you want to be a developer, you have to develop.

What Actually Matters (Especially Now)

With AI in the mix, the gap between good and bad developers is getting wider, not smaller. AI can generate code, but it can’t think for you. If you lack fundamentals, you’ll produce fragile systems that break the moment you try to change them.

The real skill set hasn’t changed:

• Understanding data flow and system design
• Working with APIs and integrating services
• Structuring applications with clear architecture
• Writing code that is simple and easy to modify

I always judged developers on two things: can I read your code easily, and can I change it without breaking everything? If the answer is no, it doesn’t matter how clever it looks.

The 80% Wall

AI-driven “vibe coding” works—up to a point. You can get something running quickly. But then you hit the wall. That last 20%—changes, edge cases, scaling—exposes every weakness in your foundation.

Messy code always shows up later as pain. You either deal with it upfront through discipline, or you pay for it when things start falling apart.

Don’t Ignore the Human Side

Most people assume this is an intellectual game. It’s not. I’ve seen very smart developers fail because they lacked discipline and consistency.

Your mental and physical state directly affects your output. If you’re tired, unfocused, and unhealthy, your thinking suffers. Simple habits—walking, basic exercise, eating properly—have a real impact on how well you solve problems.

The same goes for money. If you’re constantly under financial pressure, you make bad decisions. Living below your means gives you breathing room and better judgment.

Focus on What Lasts

Tools will change. Languages will come and go. Even AI models are interchangeable now.

What stays valuable is your ability to think in systems, write clean code, and build things that hold up over time. That’s the difference between someone who survives in this field and someone who keeps starting over.

Watch the video on YouTube here 👉 JavaScript, Java, Python … who cares. 🤷🏻‍♂️

Thanks for reading!
Stef