In my previous posts on architectural debt, I focused on the engineering side. This post focuses more on the management side, or the organisational “gearing” factors that prevent systematic technical debt reduction. You don’t have to know what distributed system architecture debt is to get any value out of this post, but if you want to know more, read this post first. When … [Read more...] about Let’s forget about architecture and just get things done!
This post is the second post on distributed system architectural debt. If you haven’t read the first post, I recommend that you read about why you acquire architectural debt and how feature-driven architecture development is a main contributor. I also there cover “abstraction debt”, the first of four types of architectural debt I cover in this series.The second type of … [Read more...] about Distributed System Architectural Debt: protocol, layering, and flow debt
In my previous post, I asked the question “Can you get 4,000+ engineers to work together?” The answer is, in the traditional “together sense”, an obvious no! However, just like ants are building an ant hill, not by talking to each other, but by each ant following a set of rules or behaviours specific to their role and by using simple signals, you can get way more … [Read more...] about Distributed System Architectural Debt: The mother of all debts! And it’s feeded by features…
I still have one or two posts I want to do on a multistream-enabled, scalable video architecture, but I have for some time also wanted to write a series on the technical scale challenges in a large, distributed engineering organisation. The fundamental problem is that the classic command and control approach with centralised planning, coordination, and program management breaks … [Read more...] about Can you get 4,000+ engineers to work together?