# Bus Factor as Seen by the Bus Driver

**URL:** <https://forum.devtalk.com/t/bus-factor-as-seen-by-the-bus-driver/240561>\
**Category:** Blogs/Articles/Talks/Podcasts\
**Tags:** elixir, blog-post\
**Created:** [9 April 2026 04:14 UTC](https://forum.devtalk.com/t/bus-factor-as-seen-by-the-bus-driver/240561 "2026-04-09T04:14:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mudasobwa](https://forum.devtalk.com/user_avatar/forum.devtalk.com/mudasobwa/32/867_2.png) [@mudasobwa](https://forum.devtalk.com/u/mudasobwa)\
**Post date:** [9 April 2026 04:14 UTC](https://forum.devtalk.com/t/bus-factor-as-seen-by-the-bus-driver/240561/1 "2026-04-09T04:14:16Z")

</div>

> It has become fashionable of late to invoke the [bus factor](https://en.wikipedia.org/wiki/Bus_factor) as though it were an inexorable law of nature, destined to bury your project the instant you hire so much as one competent specialist. Business, we are told, requires nothing but interchangeable cogs—each fitted with a correctly tuned heterodyne of work–life balance, each capable of wielding the frameworks and libraries handed down from on high—and, above all, nothing more…

> **[Bus Factor as Seen by the Bus Driver](https://rocket-science.ru/hacking/2026/04/08/bus-factor-as-seen-by-bus-driver)**
>
> Bus factor comes in two varieties. The first is provoked by saboteurs who write deliberately unreadable code. The second—far more common—arises because only one person on the team is capable of solving the hard problems, and nobody else can be...
