There was a time when I believed that becoming a better developer was all about learning more, knowing more, and mastering new languages. But then I realised, it’s not just about being better—it’s about being faster.

Some developers get so caught up in implementing a pattern that they end up with overcomplicated, hard-to-maintain code. Don’t fall into that trap!

The conventional wisdom tells us to avoid deploying software on Fridays like the plague. But as with most things, this advice isn't as black and white as it seems.

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?