Issue #313

tl;dr: Frameworks are "frames of reference that help people concentrate on what truly matters." Without discipline, the best frameworks are useless. This is the essence of leadership, and Paulo provides examples of how to develop such frameworks. 

tl;dr: Shekar provides 3 reasons: (1) Developers don’t re-read their code often enough. (2) Lack of business domain understanding. (3) Undervalue good naming. Also, helpful questions to ask: "which business concept is this functionality related to? How can I map business terms to code? What can I learn from API contracts and / or documentation of competitors?"

tl;dr: This podcast discusses the following questions: (1) What does it mean to truly treat developers as creatives within an organization? (2) What does it mean to be “developer first”? (3) How does this affect customers, product, go-to-market? 

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.