Hi, I’m Tim.
I’m a software engineer who has been writing code for a very long time. I was lucky enough to have a computer before I was 10 years old, and have always been a voracious learner in the subject.
I’ve also been an eager student of business, also from a young age. Dinner table discussions in my family usually revolved around business issues, which helped stoke my interest.
I think this is why I find the subject of technical debt so fascinating. The very term itself is a combination of two things I enjoy, and it also represents the intersection of the two subjects (as well as blending concepts from many other interesting fields).
If time and money are no object, technical debt is hardly worth discussing. When I write code for my own enjoyment, I can spend as much time as I like crafting it, much as an artist can refine their work until it makes them personally happy.
In the business world, however, time and money are far more limited. This is how technical debt becomes interesting. Technical debt tends to emerge under business pressure, and causes problems at the same time.
Technical debt affects day-to-day issues of getting work done, pushing new features, keeping customers and employees happy, as well as bigger business issues, including acquisitions (who wants to buy a business only to find out that it is a complete mess under the hood?)
I began writing a book on the subject, and I quickly realized that a better starting point would be a blog.
With this blog, I’m going to explore the (sometimes nuanced) causes, effects, and solutions of the subject. I hope you, dear reader, will enjoy reading, and (since I certainly don’t know everything) will share your stories with me as well. I’m going to enjoy it, and I hope you do too.