7 Lessons From My First 6 Months as a Developer

This post was originally written by Igor Houwat and published on the Zero To Mastery blog. To read the full version (including all 7 lessons and Igor’s full story), click here.

Six months ago, I landed my first full-time job as a developer — at the age of 38, after switching careers completely.

Since then, I’ve learned a lot. From navigating new codebases to finding my voice in meetings, the first few months have been full of challenges, wins, and growth.

In this post, I’m sharing the 5 most valuable lessons I’ve learned so far on the job — as well as what helped me get here in the first place.

Before Day One: What Helped Me Get the Job

Networking Can Be a Game-Changer

I didn’t land my first job just by cold applying — it started with a conversation.

Through a friend who had already made a similar switch into tech, I got introduced to someone at his company. That person saw potential in me and encouraged me to start learning the right skills, giving me guidance and feedback along the way.

Of course, I still had to put in the work. But the connection gave me direction and eventually helped me get a foot in the door.

Takeaway: Don’t underestimate the power of your network. Whether it’s LinkedIn, local meetups, online communities, or just friends — reach out, be curious, and look for ways to build real connections.

Master the Basics First

When I started learning, I didn’t jump into the latest frameworks. I spent over a year and a half studying the fundamentals:

• HTML, CSS, and JavaScript
• Java (to balance a statically typed language)
• Data structures and algorithms
• Functional programming and design patterns
• How programming languages and compilers work

It wasn’t flashy, but it gave me a rock-solid foundation to stand on — and made it much easier to learn frameworks later on.

Bonus: I found the basics fun. Understanding how things work under the hood gave me confidence and made me a better problem solver.

5 Lessons From My First 6 Months on the Job

1. Make a ‘Getting Started’ Plan

Your first few weeks will be a whirlwind: onboarding, learning the company culture, setting up your dev environment, reading unfamiliar code, and trying to remember everyone’s name.

It’s easy to feel overwhelmed.

Having a personal roadmap helped me stay focused. I set small goals — things like “read through this part of the codebase” or “get this basic feature working locally” — and slowly built up momentum.

Pro tip: I followed this great blog post about how to get started as a new dev. Start with small tasks, and ask lots of questions (more on that below).

2. Ask Questions (Early & Often)

It can be intimidating to speak up when you’re new. You don’t want to slow others down or look unprepared. But here’s the truth:

Asking questions is how you grow.

Most people are happy to help — especially if you’ve done a bit of homework first. Just don’t wait too long to ask if you’re stuck. A five-minute conversation can save you hours of frustration.

That said, be respectful of others’ time:

• Avoid asking the same question repeatedly
• Try to research first before asking
• Take notes so you can reference answers later

The people who grow the fastest aren’t the ones who stay quiet — they’re the ones who stay curious.

3. Find Mentors

Mentorship is a superpower in tech.

I’ve had mentors help me with technical topics, code reviews, company culture, soft skills, and more. One helped me become a better communicator. Another helped me understand our team’s coding philosophy.

Each mentor brought a different perspective — and all of them accelerated my growth.

Tip: You don’t need a formal mentorship program. If you admire someone’s work or approach, ask if they’re open to answering questions or reviewing your code now and then. Most people are flattered — and willing to help.

4. Your Age & Background Don’t Matter

I’m 38. And guess what? I’m not the oldest dev on my team.

There’s a stereotype in tech that it’s a young person’s game — but that’s just not true. I’ve met great developers in their 40s and 50s. What matters most is your ability to learn, solve problems, and communicate well.

Whether you’re coming from sales, teaching, construction, or any other field — your experience is valid. And it often brings transferable skills that make you a better teammate.

Bottom line: If you’re passionate about learning and willing to put in the work, you belong here.

5. Keep Learning

The learning doesn’t stop once you land the job — in fact, that’s when it really starts.

There’s always a new tool, a new pattern, or a better way of doing things. And that’s part of what makes software development so exciting.

After my daughter was born, I used some of my parental leave to strengthen skills I knew I’d need on the job. Even if it was just 30 minutes here or there, it made a big difference in my confidence when I came back.

Some ways I keep learning:

• Ask senior devs for feedback on my code
• Rewatch course material when I get stuck
• Write about what I’m learning (blogging is a great tool!)
• Make a habit of small daily improvements

No one knows everything. The best devs I’ve met are the ones who never stop learning.

Want to read all 7 lessons and Igor’s full story? Check out the full blog post on ZTM