tl;dr:Measuring a manager’s impact is hard since outcomes take time. This post provides early evaluation metrics as well as tips for course correction. Each of the following heuristics are explained in detail: execution, people management, team development, strategic vision & organizational influence.
tl;dr:"CAR stands for Customers, Applications, and Resources; it offers a solution to the monitoring disconnect by establishing the interactions between the three entities: the user, the application, and the underlying resources." AbdulFattah discusses how to use CAR, as well as outcomes, such as the identification of blind spots - detecting outages that would have gone unnoticed before. Exposure of long-hidden and long-standing flaws in the system, which in turn enables proper architectural fixes.
tl;dr:"This post proposes a systems-based model for diagnosing, detecting, and fixing the fundamental issues that plague engineering teams. It is a distillation of lessons acquired from identifying and implementing high-leverage strategic remedies across multiple products."
tl;dr:The first 3 are: (1) Observability: covers the spectrum of logging, metrics, distributed tracing, telemetry, alerting, etc. (2) Estimate how long it takes your team to go through the CBTD (code-build-test-debug) loop and ask yourself what that numbers tell you. (3) Flaky tests erode trust and breed learned helplessness.
tl;dr:Abdul outlines a "Maslow Hierarchy for software quality" to help you prioritize and calculate tradeoffs. The hierarchy comprises of security, usability, reliability, performance and integrity, and is explained in detail.