Introduction We’re all familiar with the idea of technical debt in software, where the velocity of development is hampered by code not being ideally suited for the task at hand. Maybe the task changed, maybe an engineer had an idea that didn’t turn out so well, maybe the data model forced an unnatural shape. for more on technical debt O’reilly has…| blog.wilcoxd.com
I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company adopt as they are growing. The one topic that gets both the most raised eyebrows, as well the most "aha!" moments is the| The Pragmatic Engineer
Introduction In my previous blog article I said: This is the topic of a future blog post: roads and feature capacity of microservice herds. Which will be a much easier conversation to have now that we understand microservices, cliques, herds, products, teams, and how enterprises mash those concepts up in different ways. Before that we need to…| blog.wilcoxd.com
Herds of microservices, flocks of people, and those that take care of them I’ve been in big enterprises, as a day job, for almost 6 years now. I’ve also been working on, and growing, a large scale microservice architecture (about 150 microservices) for about 18 months. In one way microservices give large enterprises the ability to split large work…| blog.wilcoxd.com