Kate Moriah is a technology journalist and former software engineer known for translating complex infrastructure topics into practical guidance for developers and managers. Her background in both writing and engineering allows her to explain emerging tools and cloud practices with clarity and nuance.
This article outlines key aspects of her professional focus, including observability strategies, cloud cost governance, and developer experience improvements. The structured sections and summary table below provide a quick reference to her recurring themes and concrete recommendations.
| Area | Typical Focus | Practical Outcome | Key Metric or Artifact |
|---|---|---|---|
| Observability | Metrics, traces, and logs correlation | Faster incident diagnosis | Mean time to resolution (MTTR) |
| Cloud Cost Governance | Tagging, budgeting, and showback | Reduced wasteful spend | Cost per workload or team |
| Developer Experience | Onboarding, local tooling, docs | Higher productivity and retention | Time to first meaningful deploy |
| Reliability Engineering | Chaos experiments and SLOs | Stable services under load | Error budget burn rate |
Observability and Monitoring Strategies
Kate Moriah emphasizes that effective observability goes beyond adding dashboards. Teams should instrument services to capture metrics, traces, and logs in a consistent format so correlations across signals are straightforward during incidents.
She recommends defining service level objectives early and using alerting policies that reduce noise. By aligning alert thresholds with real user impact, engineering on-call rotations can focus on meaningful signals rather than chasing false positives.
Cloud Cost Optimization and Governance
Managing cloud spend is a recurring theme in her work, with emphasis on tagging discipline, automated budget alerts, and regular cost reviews per team or product. Visibility into cost drivers helps organizations decide where to rightsize instances or switch pricing models.
Moriah often highlights the value of showback and chargeback mechanisms for accountable resource consumption. When engineers understand the cost of their experiments and deployments, they tend to make more efficient architectural choices.
Developer Experience and Tooling
Improving developer experience is central to her philosophy, covering everything from fast local development environments to clear internal documentation. Streamlined onboarding and consistent tooling reduce context switching and enable new hires to contribute quickly.
She advocates for self-service platforms that abstract complexity without hiding it entirely. When developers can provision sandboxes, view dependencies, and run tests with simple commands, they spend more time delivering features and less time managing infrastructure.
Reliability Engineering and SLOs
Kate Moriah advises defining measurable reliability goals and baking error budgets into team planning. SLOs create shared language between product, engineering, and operations, making tradeoffs between velocity and stability explicit and data driven.
Through controlled chaos experiments and postmortems focused on systemic fixes, teams can uncover hidden risks before they affect customers. This structured approach turns reliability work from reactive firefighting into a predictable engineering practice.
Key Takeaways and Recommendations
- Instrument services uniformly to enable correlation of metrics, traces, and logs.
- Define SLOs and error budgets to balance reliability with delivery speed.
- Enforce tagging standards and automate cost visibility per team or product.
- Adopt showback models to make resource consumption accountable.
- Build self-service developer platforms that reduce manual onboarding steps.
- Run small, controlled chaos experiments to validate failure modes proactively.
- Use alerting policies that prioritize user impact and reduce alert fatigue.
- Invest in documentation and internal guides to preserve team context.
FAQ
Reader questions
How does Kate Moriah define observability in practice?
She defines observability as the ability to understand internal states from external outputs by combining metrics, traces, and logs, enabling teams to diagnose issues quickly without adding excessive instrumentation overhead.
What are common cloud cost governance pitfalls she highlights?
Common pitfalls include inconsistent tagging, lack of automated budget alerts, and missing showback visibility, which together obscure true cost ownership and encourage wasteful resource use across teams.
Which developer experience improvements deliver the highest impact?
High-impact improvements include reliable local development setups, clear service templates, automated CI pipelines, and internal platforms that offer self-service access to shared infrastructure components.
How should SLOs and error budgets be balanced in fast moving teams?
She recommends starting with simple, service-level SLOs, aligning error budgets with release cadence, and using burn rate signals to throttle feature work without stifling experimentation.