Junior Dev Diaries is a blog series aimed at junior Software Engineers.
It is for developers of any career stage, but will be most helpful for juniors and intermediates. It'll cover a series of topics, from Finding Mentors to Code Reviews and more!
Sign up below to receive updates!
As a software developer, having the ability to learn and adapt is probably the most crucial skill to have. Coming at a problem with no prior knowledge, sitting down and figuring it out is what you're paid to do
Performance reviews a pretty critical in a healthy business, they let you and your manager have a frank conversation on what you are doing well, and what you could be doing better. This is your yearly or half yearly time to get feedback, grow, negotiate position and remuneration.
This series is about how to become a better software engineer, not a better programmer. What’s the differences? Well, coders write code and software engineers build multi-version, multi-person programs. Let’s focus on that multi-person element. Whether you like it or not, software engineering is a team sport.
As a junior or intermediate developer, you might be asked to give an interview. I remember the first time I was asked to interview some candidates, and quite frankly, the idea of that scared the crap out of me. Who was I to determine someone’s ability as a software engineer? Why does my opinion matter? Isn’t this a Seniors job?
As a developer in 2017, it’s important to have some form of online presence. This could be a GitHub (see my recent post), a blog, a vlog or simply just a Twitter account. I think gone are the days of Gamertags and secret online identities, and those acting as their true selves online, giving real, justified opinions, earn more respect. Subsequently having better careers as a result.
For this post, I have a bit of Q & A. These come from blog comments, DMs, tweets and the original survey. I plan to do a few more of these to give back even more, so please send your questions in, however you’d like. I’d recommend avoiding Sky Writing however, the Wellington wind may blow it away before I see it.
As an employer, or even a fellow developer, I want to see your passion for this industry. One of the best ways to do this is to have some of your favourite projects’s code open to view by me and others.
Taking part in code reviews have been one of the most interesting learning experiences in my career. I’ve done some really dumb stuff and I’ve learnt a whole lot with the over 400 reviews I’ve participated in the last 2 years. They can teach you so much about yourself and your code and I’m excited to tell you more about them...
One of the favourite parts of my career so far is getting the chance to speak publicly on topics I’m passionate about. I really enjoy working hard at work, or on side projects and learning lessons, and then being able to share those lessons with other people. It’s well known there are cultural benefits to sharing, teaching and learning, and I think it’s all ours, as humans, obligation to continue that.
Out of that announcement alone, I had several positive conversations with those in the industry. I had two conversations that led to work experience, but I had many more that led to finding some career mentors. I didn’t ask for mentors, I kept it casual, and this, I believe, was the trick to it.