Blog

Recently, a friend told me they wanted to improve their software architecture skills. They asked for some practical advice on how to get started. Rather than overwhelm them with a lengthy reading list, I thought it would be more helpful to share a few key insights I’ve picked up over the years. The core premise of this post is that software architecture isn’t just about knowing patterns, principles, and best practices.

Introduction Have you ever wondered what you should be learning to get ahead in your career? In today’s rapidly changing world, it’s easy to feel overwhelmed by the flood of trendy terms, career advice from self-proclaimed gurus, and inspiring stories of people landing six-figure jobs within months. With so many interesting new techniques and approaches available, it can be challenging to decide where to focus your limited learning time. Which skills should you invest in to truly advance your career?

Over the last few years, I have been toying with various plain text to document conversion methods. My most recent side project involved the conversion of millennia-old manuscripts into a modern, portable, digital format. This case study will outline the solution design process I followed, the trade-offs I made, and the outcomes of the initiative. Know that the process described here was done in about 30 minutes, over a cup of coffee and drawing some sketches.

The death of "Agile" In the world of software development, there is an undercurrent of people that believe that “if we can just find the right system, everything will go perfect”. If anyone ever manages to come up with the perfect cut-and-paste methodology that can be applied to any failing software project, and instantly transform it into a high-performing team, they will make millions if the marketing is adequate.