Unless you're driving the bus.

Thank you folks! It's been a great evening!  We like bus factor humor at Snrky.com.  Possibly because one of us was sort of run over by a bus. It's amusing to look back at our first run of this Snrky cartoon as we're coming up on finally republishing all of the original comics with the new artwork.  A friend once said he liked the rough art on the originals, and I used to think I did as well, but when you look at them side by side after this long, the newer ones look so much better.  Not just more artistic, but less confusing as well.  It's obvious what you're looking at when it's not an MS Paint-driven illustration.

I enjoy this particular cartoon, because it's double edged.  A negligible bus factor might actually mean you're a very responsible developer.  But that's not the implication here.  Or if it, it's implied that s/he had nothing to do with it, or is a poor enough developer that it's a natural outcome.  Maybe it's triple edged.

From Wikipedia:

"In software development, a software project's bus factor (also known as truck factor, or bus/truck number) is a measurement of the concentration of information in individual team members. The bus factor is the total number of key developers who would need to be incapacitated (as by getting hit by a bus/truck) to send the project into such disarray that it would not be able to proceed; the project would retain information (such as source code) with which no remaining team member is familiar. A high bus factor means that many developers would need to be removed before the project would necessarily fail."

Title: Unless you're driving the bus.
Snarky: One of my most important contributions is my negligible impact on our bus factor.

I think that defines his bus factor

Originally, I was going to use the snarky words, "Our manager hasn't shown up for my 1-1 in two months." With the title, "Maybe it's because he was in a car accident?"  Then I thought, that's much funnier to me because it captures the car accident that's taken me out of circulation for six weeks (so far).  But the workplace stepped up and gave me some real humor in that the one coordinated effort that seems to have suffered during my disappearance isn't my projects, which have lots of good developers and management able to handle things without me (hiring was a hiccup as I was significantly involved in that before my accident) and an agile approach that obviates some of the managerial input, but the treat list I run on a weekly basis.  Without me to issue reminders, apparently it's struggling.

Snarky has linked to the bus factor and done some humor on it before.  I just never thought I'd get to apply it personally.  For the purposes of Snarky, the bus factor meant the coauthor had to pick up all the posts.  No doubt he suffered from my bus factor more than anyone.  Keeping the site going is appreciated, and a good reason for doing everything paired, not just programming.

In software development, a software project's bus factor (also known as truck factor, or bus/truck number) is a measurement of the concentration of information in individual team members. The bus factor is the total number of key developers who would need to be incapacitated (as by getting hit by a bus/truck) to send the project into such disarray that it would not be able to proceed; the project would retain information (such as source code) with which no remaining team member is familiar. A high bus factor means that many developers would need to be removed before the project would necessarily fail. (Wikipedia, Bus Factor)

Snrky: I think it's disappointing our manager decided not to bring monthly treats anymore.
Title: I think that defines his bus factor

Unless you're driving the bus