Category: Systems
-
Software quality
Before working in an architect role, software quality seemed to me like a very abstract measure, based on ones subjective perception and experience. While hard to define, there are some attributes commonly used to evaluate quality of a software component or system. Note: as some other articles on this blog, this is a living document…
-
Normal Accident
The term “Normal accident” really caught my attention – how can an accident be normal? Are complex software systems, especially ones with technical debt and many knowledge transfers, destined to have (catastrophic) failures? Find below some quotes from the related Wikipedia articles (emphasis mine) and the reference. —- A system accident (or normal accident) is an “unanticipated interaction…
-
Grady Booch – A thread regarding the architecture of software-intensive systems.
Quoting Twitter thread by @Grady_Booch on 4th of September 2020. There is more to the world of software-intensive systems than web-centric platforms at scale.A good architecture is characterized by crisp abstractions, a good separation of concerns, a clear distribution of responsibilities, and simplicity. All else is details.You cannot reduce the complexity of a software-intensive systems;…