3 things I’ve learned in my first month as a Software Engineer

The beginning is never easy, and now I find a month has gone by since I started my role as a Software Engineering Apprentice. Every day, I’m deliberating over a new concept I’ve never heard of or getting frustrated with bugs in my code. Each time, it fuels my curiosity and desire to practice more, to get better. Here are 3 things I’ve learned in my first month as a Software Engineer:

Being a junior developer is hard: you have to embrace failing and getting things wrong. A year from now, I’ll get to look back on this moment in time and appreciate my progress. Until then, I have to be resilient and brave enough to bounce back every time I hit a hurdle.

Sometimes, being “good” is better than being “great”: Like most people, I always aim to be the best I can be, to be great. I’m learning that it’s okay to just be “good” at something. I find that it’s a healthier goal as it doesn’t encourage the perfectionism and overthinking that comes with seeking to be exceptional. This will become even more valuable as I get more meetings, tasks and projects.

Mental Health should always be a priority: I’ve always had a support system through my loved ones, but it’s great to know you have one in the workplace too. One of the best things about my workplace and training provider is that you get regular progress checks, you are encouraged to ask questions and they create a support network you can count on. So whenever I’m feeling anxious or overthinking- there’s always someone who can help me refocus and move forward with my tasks.

Being a Software Engineer is such a joyful experience for me because I enjoy the process of making things and solving problems. Many times I get lost in my work and have to be reminded that it’s lunchtime or that I have a meeting. So even when I’m sweating over tutorials or don’t remember how something works, I’m not afraid to go to the beginning and try again.