Pragmatic Engineer's Stripe profile covers a 20M-line Ruby codebase and strict API review

The issue is titled "who wants to DRI that?", and it says it covers how projects get done ^[11]. The excerpt ends before that section, so how Stripe picks a DRI, whether the role is assigned or taken up, and what happens when no one takes it all go unanswered.

The excerpt does describe the pressure the practice would operate under. Stripe processed $817B in payments in 2022, and more than 100 companies handled $1B or more on the platform ^[4]. The newsletter describes an "outsized focus on operating reliably and delivering on commercial contracts" alongside shipping hundreds of times per day ^[10]. The issue names some of the controls Stripe uses to balance speed against reliability. It says automation is at the core of everything at Stripe ^[7], and that code is rolled out gradually to reduce the chance of risky changes going wrong ^[8]. Part 2 adds a strict review of every change to Stripe's API, which goes beyond a normal code review ^[9].

In our view, a named owner is one control among several in that arrangement. Nothing here separates how much of the result comes from the owner and how much from the gates around the owner.

Transfer is the open question. Stripe was valued at around $50B in March ^[2], employs around 7,000 people ^[3], and runs a Ruby codebase of more than 20M lines ^[5]. The newsletter's author, Gergely, wrote that the issue reveals "lots of details about Stripe's engineering culture that haven't been shared before" and has takeaways for any startup building an engineering culture ^[12]. Part 2 includes the CTO's learnings on team size and on the cost of collaborating across time zones ^[13]. Team size and time zones are variables a smaller company also has, so we'd expect those learnings to be the most comparable material in the series.