I recently came to the realisation that my home network strategy was not working. Whilst running the stock ISP provided router/AP combo had worked fine for over a decade, my onboarding of more and more untrusted devices onto my network as well as the expansion of the network outside of my home’s four walls started to warrant an investment into better equipment.

My first thought was to try and survive with the basics: unmanaged switches and old router/AP combos running in access-point mode. This did work for a while, but I really struggled with getting roaming and bandwidth control to work nicely between the differently branded devices. In addition, I absolutely hated the lack of observability this solution provided.

How many times do you think a developer or development team has looked at some legacy or technical debt-laden software and exclaimed “this bollocks needs a complete rewrite!”? How many times do you think that same “complete rewrite” has led to disaster taking three, four, or more multiples of time than originally anticipated? I’d bet money on most. I’ve seen it happen. I’ve been in and led teams where it’s happened. It sucks for everyone involved.

Unit tests are tests that should test an individual section, or unit, within your code.

For a long time now, unit tests have been preached as the golden standard in most software development communities. They usually come hand in hand with another development concept: mocking. Mocking is where you ‘fake’ a dependency of the unit that you are testing, so you can test your unit in ‘isolation’.

I think the over-hyped importance of unit tests and mocking is a fallacy that is based on purism and idealism over pragmatism, realism and experience that often ends up biting you in the backside when you come to refactor only unit tested code.