Ideas from books, articles & podcasts.
Good technical design decisions are very dependent on context.
Teams that regularly work together on common goals are able to communicate regularly and negotiate changes quickly. These teams exhibit a strong force of alignment, and can make technology and design decis...
Technology governance and what is considered ‘good architecture’ is mostly considered with a ‘one size fits all’ approach.
Within a domain we have multiple teams, each being responsible for some capabilities and underlying systems within the domain.
Sometimes this is perfectly aligned, with each team being custodians of a neatly bounded set of systems. More often this is imperfect in reality, with custodi...
In the middle ground we have our vertical structure, with multiple domains. The social distance between the people in one domain and another is getting stretched.
This makes negotiation and reaching alignment more strained and slower, and so necessarily this impacts our technology choices...
When we zoom out to all of the organisation - the force of alignment between the verticals is very weak indeed. It is quite hard to make changes atomically across the landscape - mostly because the prioritisation of work for each vertical is deliberately independent.
Shared code at a whole of organisation level is limited to highly stable, highly useful things. Mostly these things are limited to libraries which can be distributed and versioned, and changed carefully.
Shared infrastructure is similar - at an org-wide level, shared infrastructure must hav...
created 4 ideas
created 16 ideas
The Independent Service Heuristics (ISH) are rules-of-thumb (clues) for identifying candidate value streams and domain boundaries by seeing if they could be run as a separate SaaS/cloud product. The ISH approach is a “rapid results” approach, and complementary to the approaches from Domain-driven Design (DDD).
❤️ Brainstash Inc.