Architecture diagrams tend to show all the individual parts rather than illustrating the system’s key purpose. Inverting this not only produces more expressive diagrams, it also improves decision making.
Real-life IT Transformation
Real life writes the best stories. This blog documents my observations from riding the architect elevator up and down Enterprise IT. Don’t miss a post – follow me on Twitter or Linkedin or subscribe to my feed.
You can also browse all posts by category.
When shifting gears, both a car and an organization need a clutch. But careful, it can be a grinder!
The key mechanism to tackle ever increasing complexity is abstraction, such as frameworks or interfaces. Some things, however, can’t be abstracted away.
A lot of modern cloud technology leverages containers. However, a non-trivial portion of enterprise applications don’t run easily in containers. The answer to this conundrum lies in taking a step back and asking a more fundamental questi...
When buying a software or hardware product for your enterprise, the future product roadmap is as much a consideration as the current product state. However, this is where some vendors play games with their customers.
Enterprise IT generally follows a “buy over build” strategy because in most cases it yields lower risk and better economics than doing it yourself. But there are a few things that you should keep to yourself.
Enterprise IT is routinely plagued by excessive complexity. It’s almost like it’s subject to the Second Law of Thermodynamics, which concludes that the entropy in a system can never decrease.
For governance to remain effective in a high-velocity environment, it needs to be automated. Surprisingly, it also produces more reliable results.