Tag: architecture

  • Why Less Is More

    - The teams that create the most value aren't the ones with the best tech. They're the ones with the clearest constraints.

  • Shaping Team Boundaries for Flow

    - How the team dependencies shapes delivery speed and what to do about it.

  • Liability Mapping your Tech Debt

    - Liability mapping splits tech debt into five categories so teams can work out what to fix and when, instead of arguing about the word 'debt'.

  • Build vs Buy vs Run

    - Self-hosting open-source tools sits between building and buying. Sometimes it's the right call, if you respect the operational cost.

  • Choose Boring Tech

    - This isn't new advice, but some reminders deserve another run: choose boring tech if you're in the business of product engineering.

  • Don't Improve Coordination, Eliminate It

    - Every cross-team sync is a boundary that needs reinforcing. What if coordination isn't a sign of organisational maturity, but a sign the boundaries are broken?