HK
Heykuki News
Top
New
Best
Ask
Show
Jobs
Toggle theme
Top
New
Best
Ask
Show
Jobs
Request
61.
▲
Clouds, Caches and Connection Conundrums
incident.io
discuss
3 years ago
peterejhamilton
4 points
62.
▲
Learning from Incidents – Formula 1
incident.io
discuss
5 years ago
vinnyglennon
4 points
63.
▲
No capes: the perils of being a hero-engineer
incident.io
3 comments
4 years ago
lawrjone
3 points
64.
▲
How to get everyone at the company to value writing
incident.io
2 comments
4 years ago
herbertl
3 points
65.
▲
The startup guide to sensible incident management
incident.io
2 comments
4 years ago
evnsio
3 points
66.
▲
How incidents made me a better engineer
incident.io
1 comment
5 years ago
lawrjone
3 points
67.
▲
Shifting left on incident management
incident.io
discuss
2 years ago
evnsio
3 points
68.
▲
How to get everyone at the company to value writing
incident.io
discuss
2 years ago
herbertl
3 points
69.
▲
Learning from incidents is not the goal
incident.io
discuss
3 years ago
sjwhitworth
3 points
70.
▲
The three pillars of great incident response
incident.io
discuss
4 years ago
kiyanwang
3 points
71.
▲
Industry Interviews: Colm Doyle, Incident Commander at Slack
incident.io
discuss
5 years ago
kiyanwang
3 points
72.
▲
Why more incidents is no bad thing
incident.io
discuss
5 years ago
sjwhitworth
3 points
73.
▲
Incidents Are for Everyone
incident.io
discuss
5 years ago
feross
3 points
74.
▲
We’re making our on-call calculator free
incident.io
3 comments
4 years ago
kiyanwang
2 points
75.
▲
Breaking down complex projects into smaller, shippable increments
incident.io
2 comments
5 years ago
lawrjone
2 points
76.
▲
Bloom filters: the niche trick behind a 16× faster API
incident.io
1 comment
2 months ago
crcastle
2 points
77.
▲
How we're shipping faster with Claude Code and Git Worktrees
incident.io
1 comment
10 months ago
blackhaj7
2 points
78.
▲
You can't vibe code a prompt
incident.io
1 comment
a year ago
ejsdev
2 points
79.
▲
Managing your resources in Terraform can be easy and fun
incident.io
1 comment
2 years ago
mooreds
2 points
80.
▲
Keep the Monolith, but Split the Workloads
incident.io
1 comment
3 years ago
Paul-Craft
2 points
81.
▲
Incident review: Intermittent downtime from repeated crashes
incident.io
1 comment
4 years ago
lawrjone
2 points
82.
▲
Ditch your overly detailed incident response plan
incident.io
1 comment
4 years ago
lawrjone
2 points
83.
▲
Building a Workflow Executor on Postgres
incident.io
1 comment
4 years ago
lawrjone
2 points
84.
▲
We're making our on-call pay calculator free
incident.io
1 comment
4 years ago
lawrjone
2 points
85.
▲
Tracing Gorm Postgres Queries with Google Cloud Tracing
incident.io
1 comment
4 years ago
arussellsaw
2 points
86.
▲
Handling third-party provider outages
incident.io
1 comment
4 years ago
lawrjone
2 points
87.
▲
Write-up of a project to reduce pager load
incident.io
1 comment
4 years ago
paprikati
2 points
88.
▲
Finding a pricing model that's just right
incident.io
1 comment
4 years ago
lawrjone
2 points
89.
▲
Building safe-by-default tools for a multi-tenant Go appp
incident.io
1 comment
5 years ago
lawrjone
2 points
90.
▲
How to avoid bad assumptions during incidents: trust, but verify
incident.io
1 comment
5 years ago
lawrjone
2 points
More