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!
So you just graduated, you need a job, your friends seemed to have got one, magically, but you’re wondering when it’s your time.
"Should I be a specialist or generalist?" Is a question it think we ask ourselves a lot as software developers.
So you’re just starting out new at a company, and maybe it’s your first software job ever. You’re faced with a new, large, unfamiliar codebase and a bug to fix.
A student asked me if they should be blogging, even though they "don't know anything".
As someone that wants to be more active with speaking, I was wondering how you manage to get speaking gigs?
In this somewhat satirical Junior Dev Diaries post, I want to cover office/tech/workplace jargon and terms.
So you want to get better at a certain language or expand your toolbox, and you’ve heard side it’s good to blog about them or open source the finished(ish) project. Great! But you just don’t know what to work on. Nothing is coming to mind and you’re not really sure where to start!
It's time for another Q&A post. This time I have two interesting questions to answer. What is a senior, and what do I do when I get stuck?
As a Junior Developer, we're often met with many different technologies, all new and foreign to us, and with someone telling us it's the next big thing and we must learn it. I've listened to those people for years now and I've found some patterns for a suitable abstraction of what types of technologies should be in your toolbox. So here there are...
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