Operations
42 bites tagged Operations — interview questions with model answers, and 60-second explainers.
Follow-the-Sun: A Global Relay Race for Work
Follow-the-sun is a global relay race for work. Teams hand off tasks to the next timezone as their day ends, enabling 24/7 coverage without requiring overnight shifts. The footgun is a poor handoff, where lost context erases all the time savings.
The Incident Commander: Direct the Response, Don't Debug
The Incident Commander (IC) is a conductor, not a soloist. During an outage, they coordinate the response, delegate tasks, and manage communication, not fix the bug themselves. This prevents chaos from uncoordinated heroics.
On-Call Rotations: Engineering Reliability Under Pressure
On-call rotations are the human backstop for service reliability, with engineers responding to alerts in minutes. This is critical for high-availability services like search or email.
SRE Engagement Models: From Gatekeeper to Platform Builder
SRE engagement models define how reliability experts help product teams, evolving from gatekeeping existing services to providing reliable platforms. This applies when scaling an SRE team's impact.
Toil: The Repetitive Work That Kills Engineering Velocity
Toil is manual, repetitive work that scales with your service, stealing time from real engineering. It's the operational treadmill of handling the same alerts or manually running scripts.
Site Reliability Engineering (SRE): Ops as a Software Problem
Site Reliability Engineering (SRE) treats operations as a software problem, using engineering to automate and scale system management. It's crucial for massive services like Google Search, ensuring availability, latency, and capacity.
Daemonizing Go/Rust Apps: Let the OS Do It
Daemonizing an app means running it as a background service, detached from your terminal. This is essential for web servers or job processors. The common footgun is writing custom daemon logic instead of using a system service manager like systemd.
Content Governance: The Rulebook for Your Content
Content governance isn't about writing; it's the rulebook for *how* content is created, managed, and retired. It defines roles, standards, and processes to ensure consistency and quality at scale. The footgun is buying a CMS without a governance plan.
Cloud Disaster Recovery: Planning for Failure
Cloud DR isn't about backups; it's a business continuity plan defining acceptable downtime (RTO) and data loss (RPO). It's for when a whole region fails or a bad deploy corrupts data. The footgun is having a plan but never testing it, creating false security.
Cloud Operating Model: Your Org's Playbook for the Cloud
A Cloud Operating Model is your org's playbook for balancing new cloud capabilities with existing systems. It's used to manage the transition to the cloud with minimal disruption. The footgun is assuming your old processes will work unmodified.
Cloud Governance: Rules for Your Cloud Kingdom
Cloud governance is like city planning for your cloud, setting automated rules to prevent chaos. It's used to control costs by blocking expensive VMs and enforce security with required settings.
Cloud Cost Management: Taming Your Bill
Treat cloud spend like a utility bill you can actively control, not a fixed cost. It's essential when your AWS, GCP, or Azure bill is growing unpredictably. The biggest footgun is treating cost management as a one-time cleanup instead of a continuous process.
SLIs & SLOs: Measuring What Matters for Service Reliability
SLIs are what you measure (e.g., latency); SLOs are the target you aim for (e.g., 99% success). They replace vague feelings about service health with concrete numbers. This is how SREs define and manage reliability.
Hotfix Deployment: Emergency Production Patches
A hotfix is a surgical strike on a production bug, using a dedicated branch to isolate the emergency fix. It's used for critical security flaws or severe defects that can't wait. The footgun: forgetting to merge the fix back into main, causing the bug to.
Structured Logging: Logs as Data, Not Strings
Treat logs as structured data (like JSON), not just plain text. This makes them machine-readable and queryable, letting you filter, search, and create dashboards on specific fields (e.g., `user_id`, `trace_id`).
Environment Variables: Configuration Outside Code
Environment variables are settings passed to your app from the outside world, letting you change behavior without touching code. Use them for API keys or database URLs. The biggest footgun is committing secrets to version control instead of using variables.
Exception Reporting: Focus on Signals, Not Noise
Exception reporting filters out the noise, showing only data that breaks predefined rules. It's used in financial reconciliation to flag mismatched transactions or to alert on system performance dips.
Log Analysis: Reading Your System's Story
Log analysis turns raw, machine-generated records into a coherent story about your system's health, security, and performance. It's crucial for debugging production failures or investigating security incidents.
Get Operations bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.