The idea is simple, have a primary respondent, and a secondary respondent. Primary First point of contact We expect immediate response We expect full ownership of incidents to be taken Secondary Backup, in case primary contact is unable to respond If the primary doesn’t acknowledge an issue within specified timeframe, secondary kicks in If the load on primary is too much, they step in Misc Make sure to clearly define escalation policies …

Repeatable steps for a Coolify managed VPS with a custom domain

Something to think about when engineering solutions.

Optimising Mean Time To Recovery is more important than trying to minimise Mean Time Between Failures.

A case study of ING bank and their experiments with team topologies

highlights, quotes, & other interesting bits from Accelerate

Various lessons and clippings from Martin Fowler.