/Management

Code Ownership And Software Quality

- Abi Noda tl;dr: "Ownership is negatively correlated with the number of bugs, and the more shared the file ownership the higher the likelihood that it will contain code defects. This trend is also supported by the fact that for all projects studied, the number of contributors is positively correlated with the number of bugs." Abi provides 4 management recommendations.

featured in #377

5 Ways To Increase Velocity By Removing The Bottlenecks  In Your QA Process

- Kirk Nathanson tl;dr: With a recession looming and many companies freezing their hiring plans, savvy teams can look at other levers to increase velocity and improve product quality. Here are five cost-effective changes you can make.

featured in #377

OKRs Are Hard

- Camille Fournier tl;dr: "In this post, I decided to write down my definition of what a good OKR looks like. My thinking has evolved from what I first learned long ago in half-remembered talks, blog posts, and books, and is now based on my experience using them to set team goals over the past ten or so years."

featured in #376

Shipping Spotify’s Culture: 5 Plugins (And 4 Principles) For Supercharging Developer Experience At Scale

- Tyson Singer tl;dr: 4 principles are DevEx at scale: (1) Keep squads fast by keeping them small, capable, and aligned. (2) Make engineering excellence and quality an everyday practice. (3) The best solutions come from the bottom up, so empower the teams doing the work. (4) Our fellow developers are our customers, so build with empathy.

featured in #376

Building Secure, Compliant Containers

- Elliot Volkman tl;dr: Containers are ideal for cloud-first organizations. However, as their use has grown, so have security incidents in container environments. Learn how to build secure containers that support business objectives.

featured in #376

Incident Categories I’d Like To See

- Lorin Hochstein tl;dr: If you’re categorizing your incidents by cause, here are some options for causes that I’d love to see used. These are all taken directly from the field of cognitive systems engineering research: (1) Production pressure. (2) Goal conflicts. (3) Workarounds. (4) Automation surprises.

featured in #376

Visual Workflow Automation. Now With Code

tl;dr: Build powerful automations fast, with all the hackability you’d expect as a developer. Stop provisioning infrastructure and maintaining one-off scripts. Build and automate cron jobs, custom alerts, and ETL tasks 10x faster with Retool Workflows.

featured in #375

Writing Docs Well: Why Should A Software Engineer Care?

- Lorin Hochstein tl;dr: Lorin recently gave a lecture in a graduate software engineering course on the value of technical writing for software engineers. There are 3 goals when writing: (1) Building shared understanding. (2) A tool for your own thinking. (3) Influence in a larger org when you’re at the bottom of the hierarchy. Lorin also advises on how to improve technical writing. 

featured in #374

How To Measure The Impact Of Your Data Team

- Tejas Manohar tl;dr: At your company, how do you measure the success of your data team? If you can’t provide hard-and-fast answers, don’t worry–you’re far from alone. Learn why you should stop focusing on metrics and why you should start tracking outcomes to measure the impact of your data team.

featured in #374

Removing Uncertainty: The Tip Of The Iceberg

- James Stanier tl;dr: "You reduce uncertainty until the software exists. You reduce uncertainty by doing: prototyping, designing, writing code, and shipping. Each of these actions serve to reduce the uncertainty about what is left to build." James discusses different methods of reducing uncertainty across a project, at various stages.

featured in #373