Great reads of the week 📑 1️⃣ Working backwards: creating effective PR/FAQ Documents by Miroslaw Stanek — Translating technical work for product teams is sometimes a hard task. Inspired by Amazon's "Working backwards" approach, Mirek created guidelines + a template for you to create great documentation (and speak the same language as business/product people) 👉 https://lnkd.in/gba9mDQR 2️⃣ How to help underperformers by 🌀 Luca Rossi — Some great insights on how to manage underperformers...and a good reminder that 80% of the issue is usually not with the individual 👉 https://lnkd.in/ggSTQNJq 3️⃣ Testing too late: a case study by Brie Ransom — Brie is THE quality engineering boss, and you can trust her when she talks about testing. And what she says is that separating programming and QA sprints leads to poor collaboration and many inefficiencies. Read her article to discover how she tackled the issue(s) 👉 https://lnkd.in/ggTn97Xq 4️⃣ Degradation vs disruption by Alex Ewerlöf — Degradation, disruption, or outage? There's more nuance between these than we think. Check out Alex's article to learn more about the concepts, and the role of a reliability engineer to mitigate those 👉 https://lnkd.in/g2DA7hNY 💌 Follow us on Substack: https://lnkd.in/eSy8mGyk
Thanks for mentioning my article. I'm glad you like it :)
Original thoughts on Reliability Engineering, Growth, and Technical Leadership
7moThanks for the shout-out. Hope your audience finds it insightful. 🙂