From the TL;DR in Tech archive, originally sent on Substack. Some links may have died since.
tl;dr in tech by Joe Karlsson - Issue #35
tl;dr: Questions worth asking when considering if a team is achieving full potential: What kind of team we are? Are the right people here? Does everyone know their role? How do we make decisions? Have we built a sense of cohesiveness? Do we know what effectiveness looks like? What happens when we disagree?
tl;dr: Shekar provides 3 reasons:
1) Developers don’t re-read their code often enough.
2) Lack of business domain understanding.
tl;dr: “One way of communicating our preparedness to our customers is through a metric called Recovery Time Objective (RTO). RTO measures the amount of time we promise it will take to recover from a catastrophic event.” Dropbox reduced its RTO by “more than an order of magnitude,” as discussed in this post.