I’m going to explain to you the concept of a paved path to software delivery.
A paved path will make your engineering job as easy as possible. It will complete every task that wastes your time and effort. It will keep you focused on delivering business value through technology solutions.
Sound good? Excellent. Let’s dive in.
It enables getting started with a clean architecture: It’s a lot easier to get started well than to get started poorly and fix it later.
The best thing you can do for your software engineering ecosystem is to add constraints.
What do I mean by constraints?
Anything that limits the degrees of freedom you have when building a software system. You might call them:
limitations restrictions standards contracts controls Regardless of what you call them, constraints will make your team better. Here are five reasons why:
#1: Constraints limit the number of decisions you have to make.
You’ve finally made it. You’ve been promoted to Enterprise Architect.
For many, this is the pinnacle of their career. For most, they arrive in their new role with an existential question:
What do I do? Nearly every organization that’s been around longer than FAANG companies is engaged in some form of software architecture modernization initiative. Over the course of my 21-year career, I’ve been privileged to work with dozens of them.
Today, I’ll teach you how to leverage The Slider Bar Principle to make better software architecture decisions.
The Slider Bar Principle teaches us that most software architecture decisions are fuzzy rather than binary. That is, the possible choices lie along a spectrum.
Understanding this principle is critical, but it’s only the first step. Using it to guide your decision-making process is the only way it can positively impact your team’s outcomes.