
Old School Burke
- Berlin
- 21 Posts
009: The Ladder of Autonomy
Understanding Task Relevant Maturity and Ladder of Autonomy
008: Complete Ownership During Incidents
There’s a constant temptation in our software engineering world to treat incidents as someone else’s problem. When your service experiences downtime because of an infra hiccup, it’s easy to say, “This is Infra's problem,” and then sit back. But if you’re the service owner,
006: Building better on-call routines for engineering teams
Mentions of on-call are usually met with grumbles.
Good reads: Mentorship
Advice on Technical Mentorship: If you're looking for practical advice on technical mentorship, John’s piece is a great resource. This article is a guide for those looking to offer technical mentorship, with practical tips on how to effectively support and guide mentees towards achieving their goals. What
Good reads: Rethinking On-Call
Rethinking On-Call: Compensation, Runbooks, and Sustainable Practices
Good reads: Observability and System Alerts
Featured Articles 1. What Makes a Good Alert? by Dan Slimmon Dan delves into the essentials of what constitutes a good alert, emphasizing the importance of alerts being actionable and informative. This piece is a great starting point for anyone looking to refine their alerting strategy to minimize noise and
Good reads: The Technical Documentation Culture
These are interesting reads for you and for your team to decide how and in what direction do you want to build your documentation culture. 1. Technical Writing Courses for Engineers by Google Developers * Kickstart your journey with Google's technical writing courses for engineers. It's your
Good reads: The art of writing
(And impact of writing)