| | How to get everyone at the company to value writing (incident.io) |
| 6 points by sjwhitworth on March 31, 2022 | past | 1 comment |
|
| | Finding a pricing model that's just right (incident.io) |
| 2 points by lawrjone on March 7, 2022 | past | 1 comment |
|
| | Kicking off projects at a small startup (incident.io) |
| 1 point by paprikati on Feb 21, 2022 | past | 1 comment |
|
| | The three pillars of great incident response (incident.io) |
| 3 points by kiyanwang on Feb 21, 2022 | past |
|
| | Designing Your Incident Severities (incident.io) |
| 17 points by lawrjone on Feb 17, 2022 | past | 2 comments |
|
| | Three pillars of great incident response: clarity, transparency and calm (incident.io) |
| 1 point by paprikati on Feb 12, 2022 | past | 1 comment |
|
| | The importance of clear writing in product development (incident.io) |
| 1 point by sjwhitworth on Feb 8, 2022 | past |
|
| | Our engineering interview process (incident.io) |
| 4 points by sjwhitworth on Feb 7, 2022 | past | 1 comment |
|
| | No capes: the perils of being a hero-engineer (incident.io) |
| 1 point by kiyanwang on Feb 7, 2022 | past |
|
| | The startup guide to sensible incident management (incident.io) |
| 3 points by evnsio on Feb 3, 2022 | past | 2 comments |
|
| | No capes: the perils of being a hero-engineer (incident.io) |
| 3 points by lawrjone on Feb 1, 2022 | past | 3 comments |
|
| | A modern data stack for startups (incident.io) |
| 5 points by lawrjone on Jan 26, 2022 | past | 1 comment |
|
| | Using context.Context to mock API clients, a reusable testing pattern (incident.io) |
| 1 point by lawrjone on Dec 21, 2021 | past | 2 comments |
|
| | Breaking down complex projects into smaller, shippable increments (incident.io) |
| 2 points by lawrjone on Dec 20, 2021 | past | 2 comments |
|
| | Building safe-by-default tools for a multi-tenant Go appp (incident.io) |
| 2 points by lawrjone on Nov 24, 2021 | past | 1 comment |
|
| | The things we find hardest in incident response (incident.io) |
| 20 points by sjwhitworth on Nov 22, 2021 | past | 1 comment |
|
| | Deploying to production in less than 5m with a hosted container builder (incident.io) |
| 4 points by lawrjone on Nov 18, 2021 | past | 1 comment |
|
| | How incidents made me a better engineer (incident.io) |
| 3 points by lawrjone on Nov 16, 2021 | past | 1 comment |
|
| | Logs and tracing: not just for production, local development too (incident.io) |
| 66 points by lawrjone on Nov 11, 2021 | past | 25 comments |
|
| | Now you see me, now you don't: feature-flagging with LaunchDarkly (incident.io) |
| 4 points by sjwhitworth on Nov 9, 2021 | past | 1 comment |
|
| | Five steps to better customer communication (incident.io) |
| 2 points by kiyanwang on Nov 8, 2021 | past |
|
| | Five steps to better customer communication (incident.io) |
| 2 points by evnsio on Oct 26, 2021 | past |
|
| | Incident.io raises $4.7m to help teams communicate during outages (incident.io) |
| 4 points by tomblomfield on Sept 30, 2021 | past | 4 comments |
|
| | How to avoid bad assumptions during incidents: trust, but verify (incident.io) |
| 2 points by lawrjone on Sept 28, 2021 | past | 1 comment |
|
| | How to avoid bad assumptions during incidents (incident.io) |
| 1 point by kiyanwang on Sept 27, 2021 | past |
|
| | The things we find hardest in incident response (incident.io) |
| 1 point by sjwhitworth on Sept 15, 2021 | past |
|
| | Industry Interviews: Colm Doyle, Incident Commander at Slack (incident.io) |
| 3 points by kiyanwang on Sept 13, 2021 | past |
|
| | Do I need an incident debrief? (incident.io) |
| 1 point by sjwhitworth on Aug 18, 2021 | past |
|
| | Learning from incidents – Formula 1 car repaired on the grid with a 17m deadline (incident.io) |
| 2 points by slyall on Aug 18, 2021 | past |
|
| | Learning from Incidents – Formula 1 (incident.io) |
| 4 points by vinnyglennon on Aug 2, 2021 | past |
|
|
| More |
