The Future of Developer Careers: When Dev and Ops Meet
summary
Argues that developers must own production by using observability not bureaucracy, showing how distributed tracing and high-cardinality data let teams map a latency spike back to a specific build, deploy or feature flag and debug in familiar code. Recommends instrumenting at the edge for breadth then drilling into a painful path for depth. Cites a case where slicing by input and code path drops 99th-percentile latency by two orders of magnitude.
AI-written summary · about
chapters (4)
related talks
29mObservability for Developers: How to Get From Here to There
46mDevOps for Java Developers (or maybe against them?!)
31mObservability for Developers: How to Get There
31mDevOps for Java Developers (Or Maybe Against Them?!)
41mDevOps for Java Developers (or maybe against them?!)
44mObservability: Superpowers for Developers
44mDevOps for developers (or maybe against them?!)
37mDevOps for Java Developers (Or Maybe Against Them?!)
