Part 1. The one-month C# sprint 🤣👉
Back in school, I was the model student—homework always finished, front-row seat, teachers' favorite. I graduated top of my class in every subject. The twist? I didn't own a computer.
University led me into finance, and I earned a Master's degree in taxation. Again, top marks. (Overachiever? Guilty.) But programming never crossed my mind.
My first job after that was four years at the tax office. It was a nightmare. I dreaded Mondays. I kept asking myself, "Is this all there is? A lifetime of paperwork and chasing overdue taxes?"
Eventually, I had enough. I decided it was time for a change. That's when I stumbled upon programming courses—JavaScript, HTML, CSS—the starter pack. This was a decade ago, and I was still working full-time. So I spent three evenings a week, three hours each, in class. By day, I was drowning in spreadsheets; by night, I was fighting with syntax errors. My social life disappeared, replaced by semicolons.
After finishing the courses, I realized that a "Hello, World!" page wasn't exactly a career launchpad. I started hunting for internships. Eventually, I found one at an IT company, but it was for C#—not JavaScript.
Here's the catch: I had zero C# knowledge. None. But I decided to embrace the "fake it till you make it" philosophy. For a full month, I lived on tutorials and caffeine. The mission was simple: learn just enough C# to survive the interview.
And it worked! I got the position. Six months in, they asked if I'd like to move to front-end development—they needed Angular folks. I figured, "Why not? How much harder can it be?" I picked up Angular, joined a project, and officially became a junior front-end developer. That was my first real IT role, and I felt like I'd pulled off a heist.
And that's how my journey in tech started—no experience, tons of late nights, and a bit of chaos.
Early on, I figured out something crucial: switching careers while holding down a job isn't about finding time—it's about making time. People often say, "I don't have time to learn something new." I get it. But if you focus on the end goal and set clear priorities, you'd be amazed at what's possible.
What worked for me (and might work for you):
- ✅️ I made learning unavoidable. I found tutorials to watch on my commute. I traded my Netflix habit for homework. I turned learning into a daily ritual that couldn't be ignored.
- ✅️ I announced my goal. Telling friends and family was my way of building in accountability. Every time they asked, "How's the coding going?" it pushed me a little further.
- ✅️ I varied my approach. Videos on the bus, practice during downtime at work, classes in the evening—it was my own custom-built bootcamp.
- ✅️ I said "yes" to every opportunity. During my internship, I wore many hats—Scrum Master, Business Analyst, QA, even automation. Whenever someone asked, "Can you handle this?" my answer was always, "Sure!" Did I always know what I was doing? Not a clue. But I figured it out.
But let's be real—I made some serious mistakes:
- 📛 I forgot to rest. I pushed so hard that I hit burnout, faced health issues, and eventually my first marriage ended. The lesson? Chase your goals, but don't forget to take care of yourself and the people around you.
- 📛 I never felt good enough. I second-guessed everything and let opportunities slip by because I didn't feel "ready." Spoiler alert: you'll never feel 100% ready. Do it anyway.
Part 2. Fighting imposter syndrome 😰
When I landed my first tech job, I was 27. Sounds impressive, right? Well, not really. My colleagues were mostly 19- and 21-year-olds straight out of university with CS degrees. Meanwhile, I was the "old" newcomer with a tax background. I kept thinking, "How will I ever keep up with them? They're going to figure out I'm a fraud." I wasn't, but it sure felt that way.
The anxiety was overwhelming, and I found comfort in chocolate. I packed on 10+ kilos trying to cope. (Silver lining: my coworkers never complained about the cake I brought in 🍰.)
But despite feeling like a fraud, I refused to give up. I kept learning and practicing, no matter how I felt.
Lessons from that era that still guide me:
- ✅️ Don't let fear block your progress. Feeling inadequate is normal—just keep moving forward.
- ✅️ Ask questions without hesitation. Nobody's going to bite.
- ✅️ Respect people's time. Google it first, or at least give it a solid try. Don't treat your colleagues like a search engine. That's what ChatGPT is for, right?
- ✅️ Write down answers you don't get, and dig deeper later. Ask an AI to break it down. I had notebooks full of cryptic notes after talking to my tech lead—looked like the scribbles of a mad scientist. But they worked!
Looking back, those early days were brutal but transformational. I didn't just learn Angular or debugging techniques. I learned how to face my fears and keep going.
Part 3: The big-company itch 🧑💻
About two years in, I set my sights on a larger company. Not a tech giant—I wasn't that bold yet. But I wanted to be at one of the biggest firms in my country.
I started preparing seriously. I spent hours studying for interviews and... failing them. Over and over. But persistence paid off, and I finally got an offer. That's when things got really interesting.
The project was demanding. I worked directly with the customer, and there was no one else on my team in my timezone. It was just me, Zoom calls, and the pressure of speaking English all day. My English back then? Let's just say it was a work in progress.
To add to the challenge, my team lead was from London, with a dry British wit that went right over my head. I spent my first few weeks panicking that they'd let me go because I couldn't crack a decent joke. Luckily, it turns out good code matters more than good banter.
That phase was about more than just coding. It taught me communication, negotiation, and pushed my English to nearly advanced level. It was tough, but completely worth it.
Key takeaways from my middle-level years:
- ✅️ Strong communication is your safety net. If you can articulate your ideas clearly, half the job is done. It also saves you from those awkward "Wait, what?" moments.
- ✅️ Never stop learning. You might feel like you've mastered things, but that's just the tip of the iceberg. Keep pushing, and you'll thank yourself later.
- ✅️ Get a mentor. A great mentor doesn't just answer questions—they show you what you didn't even know to ask.
This chapter taught me that being a developer is more than just cranking out code. It's about building connections, adapting to change, and growing as a person.
Part 4: A new beginning 👀
Okay, no Luke in this story, but there was a little Tim—my son. That's where my current journey starts. Almost 4.5 years ago, I became a mom, and everything shifted. After a six-month maternity leave, I switched companies. I prepped (while running on three hours of sleep) and secured a job at the company where I still work today.
This is where my path to senior developer—and now leader—really took off.
It hasn't been easy. This job brought incredible victories and some deep valleys. I've felt both exhilarated and exhausted. But it's also where I've grown the most.
What I've achieved so far:
- ✅️ Started mentoring others, guiding juniors, and enjoying every second of it.
- ✅️ Became an interviewer and found a passion for hiring the right people.
- ✅️ Overcame my fear of public speaking—a phobia since school days—and now love giving talks.
- ✅️ Built courses, contributed as an author, and helped others grow through mentorship.
Right now, I'm at another crossroads—shifting from senior developer to lead. And it's not just a title change. It's a complete rewiring of how I think and operate.
The real challenge
The thing is, what made me a great developer doesn't automatically make me a great leader. As a dev, I could dive deep, focus on technical problems, and write pristine code like it was my superpower. But now? That's just one part of the equation.
I've learned I need to shift my focus from code to people. (And let me tell you, people are way more complex than any JavaScript bug 🤯🐛!) My new priorities include:
- ✅️ Learning to negotiate. You can't debug humans the way you debug code. Unfortunately.
- ✅️ Thinking strategically. It's no longer about "perfect code." It's about asking, "Will this make the business happy?" And happy businesses pay the bills.
- ✅️ Delegating. I used to live by, "If you want it done right, do it yourself." That's a fast track to burnout. Now, I'm learning to trust others—even when I secretly want to snatch the keyboard.
Honestly, it feels like I'm tearing down my old foundation to build something new. It's intimidating, but also exciting.
What I'm aiming for this year
This year, I've set one big goal: to spend more time with people than with code on my screen. I want to transition from the "go-to coder" to a mentor and coach who sees the bigger picture.
Oh, and about three months ago, I started openly sharing my journey on LinkedIn. It's been an amazing experience, and I'm proud of how my personal brand is developing and the connections I'm making.
Lessons from this chapter:
- ✅️ Time management is about priorities. When you're juggling a child, a full-time job, and life in a foreign country with no backup, you learn to value every minute.
- ✅️ Development is about people, not just code. This is a truth every developer eventually has to grasp.
- ✅️ Don't be afraid to ask for help. Be open, and you'll be surprised by the support you receive.
- ✅️ Listen more than you talk. Growth comes from both knowledge and empathy.
And finally, here's a thought to leave you with: you have to believe in what you do. Even when it's hard, even when doubt creeps in, keep moving forward.
This is my story so far, but it's far from over. Who knows what's next?