An experienced software engineer, or any professional can feel just as lucky as they come to a problem they've seen before, and solve it swiftly.

The career of a software engineer is filled with and perhaps defined by troubleshooting and problem solving. I've picked up more and more tips that work for me when troubleshooting, and in this post I will lay them out for you.

The use of empty strings when used to indicate a null value or lack of value, when the language you're using has a better way to support that will, will lead to bugs and hard to maintain code. With very few exceptions, empty strings should be avoided at all costs.

I've been through the microservices transition in mature startups, large corporate and small businesses. I'm about to embark on another one with another corporate. So, what have I learned? What has worked well?

In recent times, I’ve found myself making similar mistakes in my pull requests. I thought enough was enough and it was time for a solution.

Target State Architecture (TSA) is your architecture, perfected. However, the problem for most companies is that it lives in the back of the mind of the most senior or long-serving engineers. Maybe the CTO knows, but not many others would. Some engineers might know bits of the future and most likely only know bits of the present.

I was recently contacted by a 14 year old student based in the UK, and they had some questions for me about my career and job.

This post is about bad engineers, and one aspect of them in particular - solution favouritism.

Soft Skills makes the term sound secondary or less important. This connotation couldn't be further than the truth.

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.