| | Who watches the watchers? How we page ourselves if incident.io goes down (incident.io) |
|
5 points by rorymalcolm 13 days ago | past | 2 comments
|
|
| | Observability as a Superpower (incident.io) |
|
6 points by kiyanwang 22 days ago | past | 1 comment
|
|
| | Continually testing our product with smoke tests (incident.io) |
|
1 point by kiyanwang 3 months ago | past
|
|
| | Building On-call: Our observability strategy (incident.io) |
|
2 points by sjwhitworth 3 months ago | past
|
|
| | What a 2024 data stack looks like (incident.io) |
|
2 points by sjwhitworth 4 months ago | past
|
|
| | Building a multi-platform on-call mobile app with React Native in 2024 (incident.io) |
|
5 points by rorymalcolm 4 months ago | past | 4 comments
|
|
| | Managing your resources in Terraform can be easy and fun (incident.io) |
|
2 points by mooreds 5 months ago | past | 1 comment
|
|
| | Shifting left on incident management (incident.io) |
|
3 points by evnsio 8 months ago | past
|
|
| | How to get everyone at the company to value writing (incident.io) |
|
3 points by herbertl 8 months ago | past
|
|
| | Incident.io On-Call (incident.io) |
|
6 points by louis-paul 9 months ago | past | 7 comments
|
|
| | Debugging Go compiler performance in a large codebase – incident.io (incident.io) |
|
1 point by rbanffy 10 months ago | past
|
|
| | Lessons learned from building our first AI product on OpenAI (incident.io) |
|
4 points by samspenc 10 months ago | past | 1 comment
|
|
| | Code Generation with Go Generics (incident.io) |
|
5 points by veqq 11 months ago | past | 1 comment
|
|
| | A modern data stack for startups (2022) (incident.io) |
|
58 points by olestr 11 months ago | past | 26 comments
|
|
| | [dupe] Tracking developer build times to decide if the M3 MacBook is worth upgrading (incident.io) |
|
32 points by sharjeelsayed 11 months ago | past | 2 comments
|
|
| | Tracking developer build times to decide if the M3 MacBook is worth upgrading (incident.io) |
|
653 points by paprikati 11 months ago | past | 408 comments
|
|
| | AI convinced our CTO to upgrade our MacBooks (incident.io) |
|
4 points by rdoherty 11 months ago | past | 1 comment
|
|
| | How AI convinced our CTO to upgrade our MacBooks (incident.io) |
|
4 points by idoco 11 months ago | past
|
|
| | How AI convinced our CTO to upgrade our MacBooks (incident.io) |
|
7 points by disintegrator 11 months ago | past | 3 comments
|
|
| | A guide to incident post-mortem documents (incident.io) |
|
4 points by alexzeitler on Oct 22, 2023 | past
|
|
| | Clouds, Caches and Connection Conundrums (incident.io) |
|
4 points by peterejhamilton on Sept 26, 2023 | past
|
|
| | Learning from incidents is not the goal (incident.io) |
|
3 points by sjwhitworth on May 11, 2023 | past
|
|
| | Keep the monolith, but split the workloads (incident.io) |
|
230 points by kiyanwang on April 24, 2023 | past | 157 comments
|
|
| | How we built it: incident.io Status Pages (incident.io) |
|
4 points by Sinjo on April 20, 2023 | past | 1 comment
|
|
| | Keep the Monolith, but Split the Workloads (incident.io) |
|
2 points by Paul-Craft on April 19, 2023 | past | 1 comment
|
|
| | Making transparency a principle of your company’s culture (incident.io) |
|
1 point by mooreds on Feb 17, 2023 | past
|
|
| | Building great developer experience at a startup (incident.io) |
|
1 point by herbertl on Dec 5, 2022 | past
|
|
| | How to get everyone at the company to value writing (incident.io) |
|
3 points by herbertl on Dec 4, 2022 | past | 2 comments
|
|
| | Incident review: Intermittent downtime from repeated crashes (incident.io) |
|
2 points by lawrjone on Dec 3, 2022 | past | 1 comment
|
|
| | Postmortem on downtime due to handling of Go panics (incident.io) |
|
1 point by sjwhitworth on Dec 2, 2022 | past
|
|
|
|
More |
