How we page ourselves if incident.io goes down #IncidentResponse #Reliability #OnCall
We're opening a San Francisco office #Tech #Business #Startup
Organizing ownership: How we assign errors in our monolith #Engineering #Software #Reliability
How we handle sensitive data in BigQuery #Data #Security #Cloud
How we model our data warehouse #DataModeling #Tech #Engineering
Lessons from 4 years of weekly changelogs #Engineering #Productivity #DevOps
Observability as a superpower #Observability #Reliability #DevOps
Behind the Flame: Navo #IncidentResponse #Reliability #SoftwareEngineering
Choosing the right Postgres indexes #Postgres #Database #DevOps
Mastering regulatory compliance with incident.io #Compliance #Regulation #IncidentResponse
What is a SEV1 incident? Understanding critical impact and how to respond #IncidentResponse #Reliability #SoftwareEngineering
Why I like discussing actions items in incident reviews #IncidentResponse #SoftwareEngineering #DevOps
incident.io is best in class for momentum, relationships and enterprise adoption #Reliability #Engineering #Product
The ultimate guide to on-call schedules #OnCall #Engineering #Reliability
Data quality testing #DataQuality #Testing #SoftwareEngineering
A new era for Catalog #Engineering #Reliability #SoftwareDevelopment
Building On-call: Our observability strategy #OnCall #Observability #DevOps
Introducing: incident.io for Microsoft Teams #Tech #SaaS #DevOps
Building On-call: Continually testing with smoke tests #OnCall #SoftwareEngineering #Reliability
Introducing SEV0 #IncidentResponse #Reliability #DevOps