Home / Companies / Incident.io / Hacker News

Incident.io on HN

56 posts with 1+ points since 2022

Filters
Since:
Posts by Month (56 total)
Hacker News Posts
Title Points Comments Date
Tracking developer build times to decide if the M3 MacBook is worth … 653 -- 2023-12-28
Keep the monolith, but split the workloads 230 -- 2023-04-24
A practical guide to incident management 132 -- 2022-06-16
A modern data stack for startups (2022) 58 -- 2023-12-30
Designing Your Incident Severities 17 -- 2022-02-17
Incident.io Raises $62M 13 -- 2025-04-10
Bloom filters: the niche trick behind a 16× faster API 7 -- 2025-11-16
Incident.io On-Call 6 -- 2024-03-05
How to get everyone at the company to value writing 6 -- 2022-03-31
Observability as a Superpower 6 -- 2024-11-18
Building a multi-platform on-call mobile app with React Native in 2024 5 -- 2024-07-16
Incident.io Raises $34M 5 -- 2022-07-13
Code Generation with Go Generics 5 -- 2023-12-30
A modern data stack for startups 5 -- 2022-01-26
Who watches the watchers? How we page ourselves if incident.io goes down 5 -- 2024-11-27
The Incident Maturity Model 5 -- 2024-12-23
Lessons learned from building our first AI product on OpenAI 4 -- 2024-01-17
How we built it: incident.io Status Pages 4 -- 2023-04-20
How we built our workflow engine 4 -- 2022-09-14
Our engineering interview process 4 -- 2022-02-07
A guide to incident post-mortem documents 4 -- 2023-10-22
Clouds, Caches and Connection Conundrums 4 -- 2023-09-26
The flight plan that brought UK airspace to its knees – incident.io 4 -- 2025-02-28
No capes: the perils of being a hero-engineer 3 -- 2022-02-01
How to get everyone at the company to value writing 3 -- 2022-12-04
The startup guide to sensible incident management 3 -- 2022-02-03
Shifting left on incident management 3 -- 2024-04-10
Learning from incidents is not the goal 3 -- 2023-05-11
The three pillars of great incident response 3 -- 2022-02-21
We’re making our on-call calculator free 2 -- 2022-09-12
Managing your resources in Terraform can be easy and fun 2 -- 2024-07-08
Incident review: Intermittent downtime from repeated crashes 2 -- 2022-12-03
Ditch your overly detailed incident response plan 2 -- 2022-10-03
Building a Workflow Executor on Postgres 2 -- 2022-09-30
What I learned as employee #2 at a scaling startup – year … 2 -- 2022-09-13
Tracing Gorm Postgres Queries with Google Cloud Tracing 2 -- 2022-07-11
Handling third-party provider outages 2 -- 2022-07-04
Write-up of a project to reduce pager load 2 -- 2022-04-22
Finding a pricing model that's just right 2 -- 2022-03-07
Building On-call: Our observability strategy 2 -- 2024-08-23
What a 2024 data stack looks like 2 -- 2024-08-09
How DORA will impact incident management at financial entities 2 -- 2022-08-16
You can't vibe code a prompt 2 -- 2025-03-27
How we're shipping faster with Claude Code and Git Worktrees 2 -- 2025-08-10
Breaking through the Senior Engineer ceiling 2 -- 2025-08-09
Incident.io Service disruption on October 20, 2025 2 -- 2025-10-23
How to empower your team to own incident response 1 -- 2022-05-21
Making Go errors play nice with Sentry 1 -- 2022-04-06
Kicking off projects at a small startup 1 -- 2022-02-21
Continually testing our product with smoke tests 1 -- 2024-09-02
Debugging Go compiler performance in a large codebase – incident.io 1 -- 2024-01-23
Making transparency a principle of your company’s culture 1 -- 2023-02-17
Building great developer experience at a startup 1 -- 2022-12-05
A new channel per incident – helpful or harmful? 1 -- 2022-09-19
Declare early, declare often: why you shouldn’t hesitate to raise an incident 1 -- 2022-06-13
The importance of clear writing in product development 1 -- 2022-02-08
Plushcap, by Matt Makai. 2021-2026.