Overcome the fear of selling yourself

Most would admit to wanting more feelings of purpose. We spend most of our time at our jobs. It would be logical, then - to ensure that our jobs have this purpose. If you're a developer and you don't have "a speciality", "a niche" or "a brand". It could be the first step you take towards achieving feelings of purpose.

I’d always hated the idea of “selling” myself. The thought of interviews made me sick. It felt so egotistical. I even asked my father to fill out the about me section of my CV. I couldn’t bring myself to do it.

What the hell is “The socratic method” and why as a developer you should care

Teaching is a lesser flexed muscle of the software developer. Yet, being a strong teacher can enable a strong team and a strong career.

As software developers, we’re always teaching each other. It’s a core part of what we do. Yet, most developers get little formal training in areas outside of software developing. Most developers wouldn’t think to read a book on teaching to improve their career. But, doing just that could make some profound changes to your career and your team. 

5 steps to bulletproof behavioural interview prep

Behavioural questions are often very difficult. Yet with a little preparation anyone can nail them with ease.

After a lot of failures I’ve created a method that allows me to nail those behavioural questions. Behavioural questions often look a little like this:
  • “Identify and explain a time when you utilised leadership?”
  • “Identify and explain a time when you had to manage a conflict?”
  • “Describe a complex problem to me”
Behavioural questions can seem impossible to prepare for. It seems impossible to remember enough scenarios to cover it all. Especially, like me, you struggle with thinking on your feet. But that’s where good preparation comes in.

The Importance Of The Developer Portfolio

Throughout my early jobs – many comments were made positively about my portfolio. I had a hunch at the time that having a portfolio was important. It was only until later in my career, when I was performing interviews that I realised just how useful a portfolio is to hiring managers and organisations.

Back when I first started development, I spent one year working for a company in London when I caught the bug for being a developer, it was only after this point that I started to work on and create a portfolio. Luckily it wasn’t “too late” and I had retained a lot of the information and work from my university to be able to upload it.

Becoming an irreplaceable junior software developer

As a junior developer it's easy at times to feel a little lost. Yet there are things you can do to increase your own productivity.

You’ve started a job as a junior developer. You’re getting used to the team. Maybe you feel a bit lost on where you can best contribute to the team? Luckily there area areas you can focus on to make an immediate impact.

Cultivated specific expertise

Most teams have a skill deficit in a certain area. This could be CSS, databasing, agile working. If you can find and identify these skill deficit areas you can provide incredible value to your team.
Focused effort on a specific topic can create a mastery in a shorter time than you might realise. As software developers we’re required to understand such broad topic areas. This means the rest of your team might be feeling the pains of spreading themselves too thin.
This poses a great opportunity within your team. Rather than trying to keep up with every area instead focus on only one. Master that. And then move on to the next. With this approach you will soon find others coming to you for support in your area(s) of expertise. It takes patience but it can make all the difference.

Support the team

Often most developers will shy away from doing “managerial tasks”. Things like organising tasks, unblocking members of the team and anticipating issues. If you notice this trend, you can offer to take up some of these tasks. Soon, the team will soon be seeing you as an essential part of the operation.


As a junior developer, it’s easy to feel like a spare part. But we must remember that we’re operating on a team. This means that team output is far more important than our output as individuals. By noticing this we can start to see far more tasks that are within our grasp when joining a new team.