Today in Bulgaria, we celebrate the Day of the Bulgarian Alphabet – a day rooted in the spirit of learning, creation, and growth. It honors Saints Cyril and Methodius, whose work in the 9th-10th century led to the development of the Glagolitic alphabet, the foundation of the Cyrillic script used across much of Eastern Europe today.
By creating our letters, they built a system to pass on knowledge and gave the start of something that would empower an entire nation. But it was their students who were the ones thanks to whom we speak Bulgarian today. They took what was given to them, improved it, and spread it across kingdoms.
That’s how legacies are born.
The Parallel I Can’t Ignore
I love drawing parallels, and I can’t ignore this one with my own profession – that of an engineering manager in software development.
Whether we like it or not, once we gain some experience, we become the teachers. It’s our job to guide juniors, just as the disciples were once guided.
But here’s a truth that often gets overlooked in our industry:
Being a junior is a temporary stage, not an identity.
The Entitlement Problem
I’ve seen it too many times. Junior developers who treat their lack of experience as a shield. A reason to avoid responsibility. An excuse to demand endless hand-holding.
“I’m just a junior” becomes a get-out-of-jail-free card for:
- Not reading documentation
- Expecting seniors to solve their problems
- Avoiding difficult tasks
- Not taking ownership of their growth
This mindset is poison.
Cyril and Methodius wouldn’t have achieved greatness if their students had stayed passive. They taught so their students could build. The same applies today.
What Juniors Get Wrong
Here’s what I tell every junior developer I mentor:
Your title doesn’t entitle you to comfort, shortcuts, or endless hand-holding.
If you want to move forward, you must walk it yourself. Yes, we’ll guide you. Yes, we’ll review your code. Yes, we’ll answer questions.
But we won’t do your job for you.
The juniors who succeed are the ones who:
- Ask questions after trying first
- Take feedback and implement it immediately
- Look for opportunities to contribute
- Read the docs before asking
- Own their mistakes and learn from them
The ones who struggle? They wait for someone to “take care of them” because of their lack of experience.
The Temporary Stage Mindset
Being junior is measured in months, not years.
I’ve seen developers go from junior to mid-level in 18 months. I’ve also seen developers stuck at junior level for 5 years.
The difference? Mindset.
The ones who grow treat “junior” as a temporary constraint to overcome. They:
- Take what they’re given (advice, feedback, code reviews, learning opportunities)
- Run with it
- Build on it
- Share it with others
The ones who stay junior treat it as an identity. Something fixed. Something that defines them.
It’s not.
What Success Looks Like
A successful junior-to-mid transition looks like this:
Month 1-3: Dependency “How do I do X?” “What does Y mean?” “Can you review this?” Normal. Expected. Fine.
Month 4-6: Semi-independence “I tried X but got stuck at Y.” “I think we should do Z, but wanted to confirm.” Better. They’re trying first. Good sign.
Month 7-12: Independence with validation “I implemented X using Y approach. Deployed to staging. Can you review?” Excellent. They’re shipping. Just need final validation.
Month 12-18: True ownership “Noticed a problem with X. Fixed it. Here’s the PR. Also documented it.” This is it. They’re not junior anymore.
The Hard Truth
This industry moves fast.
Those who stay curious, accountable, and resilient are the ones who grow.
The rest? They stay junior—not because of their years, but because of their mindset.
I’ve mentored developers who went from bootcamp grad to senior in 3 years. I’ve also worked with “junior” developers with 6 years of experience who still can’t work independently.
The difference is never talent. It’s always mindset.
It’s Not Too Late
If you’re reading this and recognizing yourself in the “stuck junior” category, don’t panic.
It’s not too late for you.
But it will be if you waste your time waiting for help instead of learning how to lead.
Here’s what you can do starting tomorrow:
1. Stop asking before trying Spend 30 minutes genuinely attempting to solve the problem first. Google it. Read the docs. Experiment.
2. Own your PRs Don’t submit code you wouldn’t want to maintain. Review it yourself first. Test it thoroughly. Add comments.
3. Learn one new thing per week Not passively. Actively. Build something with it. Write about it. Teach it to someone.
4. Seek feedback aggressively Don’t wait for annual reviews. Ask your tech lead monthly: “What should I improve?”
5. Help other juniors Teaching is the fastest way to learn. Answer questions on your team Slack. Write documentation. Share what you’ve learned.
The Legacy We Build
Let’s honor the legacy of those who taught before us—not by expecting ease, but by earning our place through learning, creating, and helping others rise.
The alphabet wasn’t created so we could memorize letters. It was created so we could write our own stories.
Your career is no different.
You’ve been given the tools. The rest is up to you.
To my Bulgarian readers: Честит 24-ти май! 📚
To everyone else: Stop waiting. Start building.