How much time are you going to spend stressing about whether you chose the “right” language to start your career?
If you are a junior developer or an entry-level engineer looking to kickstart your career without getting overwhelmed by constant stack changes, then this email is for you.
In today’s issue, I want to share why your ability to adapt matters infinitely more than mastering a single language, and how you can position yourself as a problem solver from day one.
Before you continue, if you enjoy my work and would like to support the newsletter, I’d really appreciate it if you shared it with a fellow engineer:
💚 On WhatsApp | 💙 On LinkedIn | 🩵 Bluesky
Or simply forward this email to someone who might find it useful.
Forget Language Dogmas: Your Superpower is Flexibility
When you are starting, it’s easy to feel like you must become a “Java developer” or a “Python developer.” But here’s a secret from the trenches:
☝🏼 Companies don’t hire you for your loyalty to a syntax; they hire you to build solutions. Check this out.
Imagine your team decides to migrate a service from Java to Rust. If you freeze up because you haven’t mastered Rust yet, you get stuck. But if you embrace the opportunity, ask questions, and treat Rust as just another tool to solve the problem, your team will notice your value immediately.
👉🏼 Demonstrating an open disposition to pick up whatever language the project needs is what will set you apart from every other entry-level candidate.
Good, language flexibility gets your foot in the door... Now, how do you thrive when tools like AI are writing code faster than ever?
Stop Thinking of Yourself as Just a “Coder”
It’s easy to measure your progress by how many lines of code you write each day, but AI tools are changing that dynamic rapidly.
AI is simply another layer of abstraction in software history, just like the jump from assembly code to Python. You don’t need to fear it; you need to leverage it.
☝🏼 Keep in mind: Your job isn’t to be a human syntax generator. Your real job is learning how systems fit together and understanding the business problem you are solving.
Instead of spending hours trying to memorize boilerplate syntax, use AI tools to handle repetitive code so you can spend your energy understanding software architecture, debugging logic, and learning trade-offs.
Last part: how do you handle the fear of stepping into topics you don’t know yet?
Embrace the Discomfort of Being New
Starting in tech means facing things you don’t know every single day. That uncertainty can feel overwhelming, but it’s actually where your biggest career leaps happen.
Stepping out of your comfort zone and taking calculated risks, like volunteering for a task in a framework you’ve never used, is how you grow from junior to senior.
👉🏼 Treat every moment of confusion not as a failure, but as proof that you are leveling up your engineering skills. I know this sounds simple, but indeed, it is not. Practice it; don’t give up.
Good, those were the core mindsets to keep close... Let’s wrap up for today and summarize what you can put into practice right now.
✨ Summary
👉🏼 Prioritize flexibility over tools: Being eager to learn whatever language the business needs (e.g., shifting from Java to Rust) makes you stand out much more than knowing just one framework.
👉🏼 Evolve into a problem solver: Don’t limit your worth to writing raw code; leverage AI abstractions to focus on system design and business context.
👉🏼 Lean into the unknown: Get comfortable being uncomfortable; taking smart risks early on is the fastest engine for your growth.
Drop a message in the comments or reply to this email, I read and reply to all!
Best,
Marcos.