sjwhitworth
- Karma
- 344
- Created
- April 28, 2014 (12y ago)
- Submissions
- 0
- Building On-call: Our observability strategy (incident.io)
- What a 2024 data stack looks like (incident.io)
- Learning from incidents is not the goal (incident.io)
- Postmortem on downtime due to handling of Go panics (incident.io)
- Incident.io Raises $34M (incident.io)
- Handling third-party provider outages (incident.io)
- How to get everyone at the company to value writing (incident.io)
- The importance of clear writing in product development (incident.io)
- Our engineering interview process (incident.io)
- The things we find hardest in incident response (incident.io)
- The things we find hardest in incident response (incident.io)
- Tom (Monzo) thoughts on early stage fundraising (docs.google.com)
- Do I need an incident debrief? (incident.io)
- Postgres sequences can skip 32 unexpectedly (incident.io)
- What Is an Incident? (incident.io)
- Why more incidents is no bad thing (incident.io)
- Incidents Are for Everyone (incident.io)
- Incidents Are for Everyone (incident.io)
- Don't count your incidents, make your incidents count (incident.io)
- Backstage: A New Home for Engineers (highgrowthengineering.substack.com)
- Semgrep: A Swiss Army knife for understanding code (highgrowthengineering.substack.com)