/Management

Build Times And Developer Productivity

- Abi Noda tl;dr: The takeaway is that even modest improvements to build times are helpful. Three things: (1) There is no specific threshold for how fast builds need to be for developers to stay on task and be productive. (2) Providing developers with estimated build times can improve productivity. (3) Even modest improvements in build latency can be helpful.

featured in #431

The Ultimate Guide To Developer Experience

- Ari-Pekka Koponen tl;dr: Investing in developer experience is a bit of a no-brainer if you want to improve developer retention and productivity. But what are some practical ways to drive great DX in your organization?

featured in #431

Right-Sizing Your Technology Team

tl;dr: Authors provide insight into the following questions: (1) Do we have enough developers? (2) Are we paying more than we need to for our development efforts? (3) Why isn’t the software our developers are creating delivering the outcome we wanted to see? (4) Can we wind down or repurpose the number of developers maintaining some of our internal and legacy software capabilities? (5) Why is the value of our software falling?

featured in #431

Embracing Failure

- Mike Fisher tl;dr: "Frame failures like a video game, and you'll not only iterate more and learn faster but also sweeten the taste of subsequent successes." Mike discusses how reframing failure as a learning opportunity and decoupling it from professional evaluations, businesses can foster an environment of boldness and innovation.

featured in #430

Gelling Your Engineering Leadership Team

- Will Larson tl;dr: Will discusses: (1) Debugging the engineering leadership team after stepping into a new role. (2) Gelling your leadership into an effective team. (3) What to expect from your direct reports in that leadership team. (4) Diagnosing conflict within your team.

featured in #430

Five Reasons To Trust Prolific Participants With Your AI Training Tasks

- George Denison tl;dr: Finding engaged and reliable participants for your AI training tasks can be a challenge. Here are five reasons why you can trust Prolific participants with your AI training tasks. Prolific participants are: (1) Engaged. (2) Diverse. (3) Treated fairly and ethically. (4) Understand their crucial role. (5) Satisfied.

featured in #430

Readability: Google's Temple To Engineering Excellence

- Brian Kihoon Lee tl;dr: Brian shares his experience as a readability mentor at Google and reflects on its cultural significance within the company. While he doesn't recommend implementing Google's version of readability in other companies, he proposes a variant called "Readability Lite" that focuses on consensus on readability standards, mentorship programs, and non-blocking mechanisms to encourage engineers to strive for mastery.

featured in #430

Bottlenecks vs Bandpass

- Andrew Bosworth tl;dr: To avoid bottlenecks in product development, horizontal teams should establish clear guidelines and standards, allowing vertical teams to work efficiently. This frees up time for horizontal experts to focus on complex issues and enables faster progress in the future.

featured in #429

People Love Snowflake, But…

tl;dr: Delivering sub-second analytics over large datasets can get pricey. When it comes to optimizing performance and cost, there are many great players. See how Snowflake compares to Firebolt, Clickhouse, Databricks, and more in the [2023 Cloud Data Warehouse Comparison Guide](https://hi.firebolt.io/lp/cloud-data-warehouse-comparison?utm_source=referral&utm_medium=pointer&utm_campaign=comparison).

featured in #429

2023 Cloud Data Warehouse Comparison Guide

tl;dr: 2023 Cloud Data Warehouse Comparison Guide

featured in #429