# bus factor A software-project resilience metric measuring the number of key developers whose loss would make the project unable to proceed. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Software Engineers Should Emphasize the Impact of Their Work DevFeed: [Why Software Engineers Should Emphasize the Impact of Their Work]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-06-09T12:46:03Z Content type: opinion Language: en Sources: [Saiyan Growth Letter]() Topics: [Software](), [bus factor](), [lead time](), [Learning]() Tags: [bus-factor](), [lead-time](), [learning](), [promotion](), [results](), [software-engineer](), [team]() ### AI overview The article argues that software engineers should track and communicate the impact of their work, not only the tasks they completed. It uses organizing a weekly learning session as an example, linking that activity to a larger bus factor, shorter lead time, faster delivery, and happier customers. ### Source excerpt Input never matters. Outcome does. ## How to lead weekly sessions for your team DevFeed: [How to lead weekly sessions for your team]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-02-21T15:03:33Z Content type: tutorial Language: en Sources: [Saiyan Growth Letter]() Topics: [sessions](), [bus factor](), [Learning](), [context]() Tags: [bus-factor](), [how-to](), [learning](), [minutes](), [remote]() ### AI overview A practical guide to leading weekly learning sessions for a remote team. It covers common organizational mistakes and recommends using an agenda, communicating presenters, recording sessions, sharing materials, and preparing at least a week in advance to respect teammates' time and energy. ### Source excerpt Care about your teammates' time and energy. ## How Code Reviews Support Chromium's Code Quality and Team Resilience DevFeed: [How Code Reviews Support Chromium's Code Quality and Team Resilience]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2014-03-31T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [Code](), [Chromium](), [code style](), [bus factor]() Tags: [bus-factor](), [chromium](), [code](), [code-reviews](), [code-style]() ### AI overview The article explains how Chromium uses code reviews and style guides to manage a large, actively changing codebase. It argues that review helps catch broken or poor-quality code, maintain consistency, and reduce reliance on a small number of contributors. ### Source excerpt Stats: a preamble I've been reading too much about March Madness brackets, so I thought I had to run some numbers around here like the cool kids do. Get your umbrella out, it's about to rain cold facts. In the history of time, Chromium has had 205,095 commits made by 1,943 contributors representing 7,431,088 lines of code. In the last 30 days, there have been 5021 commits, by 637 contributors, including 53 new hoomans. I did some advanced Nate Silver analysis here for you, and that's at least 167 commits and 1+ new committers a day. On average, that's at least 7 commits an hour. Every hour. All of the hours. That's an imperial ton of new code being added, by what it seems like new people. Imagine if everyone could commit code willy-nilly. Are you imagining a minefield? You should. Code reviews ftw Good news for our browser using audience! Chromium isn't a minefield, and on top of it, has pretty awesome looking code. This comes from the fact that any code changes need to be reviewed and blessed before they can land on the master branch. More eyes means less bugs means you're less likely to commit broken code and break the internet. And you really don't want to break the internet. Even if you have tests, and everything is going your way, you can write correct, but genuinely shitty code. 7 million lines of kinda-shitty code is not something anyone wants to work with, and are worth investing a little time in fixing. Code reviews also bring up the bus factor, which is my favourite sinister nerd metaphor. You know, the buuuuuus factor. The number of people that can get run over by a bus on a team before that team is royally and epically screwed. If all the code that you write has been closely read by a different person, then you're probably ok getting run over by a bus every once in a while. But still, you probably shouldn't. Who would feed your cat? Consistent code is the best code Code style guides are sooper neat, and are a huge part of code reviews, because ain't nobo