home.social

#busfactor — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #busfactor, aggregated by home.social.

fetched live
  1. Bus-factor склада: как считать зависимость от ключевых руководителей

    В инженерии программного обеспечения есть метрика bus-factor — минимальное количество людей, одновременная потеря которых останавливает систему. Чем выше число, тем устойчивее операция к кадровым изменениям. В IT эту метрику считают регулярно. На складах — почти никогда. При том что текучесть персонала в складской отрасли составляет около 49% в год. Склад, который не знает своего bus-factor, не знает, насколько каждый такой уход приближает его к операционному сбою. Важная оговорка до расчёта: bus-factor — не оценка компетентности. Высокий bus-factor у конкретного человека означает, что склад правильно спроектирован вокруг этой роли. Низкий — что знание об операции сосредоточено в одном месте и нигде больше не зафиксировано.

    habr.com/ru/companies/intekey/

    #busfactor #складская_логистика #wms #управление_рисками #автоматизация_склада #управление_знаниями #текучесть_кадров #intekey

  2. While planning my NAS build, I had a sobering realization. My "Bus Factor" at home is exactly 1.

    I'm going to spend so much time securing my data against drive failures and hackers but what about my family? If something happens to me, my homelab becomes a digital tomb that no one has the keys to.

    I dug up this repo I bookmarked a while ago: eol-dr (End of Life / Disaster Recovery). It’s basically a framework for documenting your digital life for your loved ones.

    GitHub: github.com/potatoqualitee/eol-

    Configuring a RAID array is easy. Writing a "How to access our photos when I'm gone" guide is the hard part. Probably, the hardest. But it's arguably the most important backup you'll ever make.
    Hope it'll be useful for somebody. Just make a star and take a look later when you feel it's a time.

    #SelfHosted #Homelab #DigitalLegacy #OpSec #SysAdmin #Privacy #LifeTips #BusFactor #Backup #Nas #Death #Thoughts #Blog

  3. While planning my NAS build, I had a sobering realization. My "Bus Factor" at home is exactly 1.

    I'm going to spend so much time securing my data against drive failures and hackers but what about my family? If something happens to me, my homelab becomes a digital tomb that no one has the keys to.

    I dug up this repo I bookmarked a while ago: eol-dr (End of Life / Disaster Recovery). It’s basically a framework for documenting your digital life for your loved ones.

    GitHub: github.com/potatoqualitee/eol-

    Configuring a RAID array is easy. Writing a "How to access our photos when I'm gone" guide is the hard part. Probably, the hardest. But it's arguably the most important backup you'll ever make.
    Hope it'll be useful for somebody. Just make a star and take a look later when you feel it's a time.

    #SelfHosted #Homelab #DigitalLegacy #OpSec #SysAdmin #Privacy #LifeTips #BusFactor #Backup #Nas #Death #Thoughts #Blog

  4. @b9AcE @fedora @kde

    Also apparmor is used instead of selinux. And it was maintained afaik from only one person #busfactor But besides these interesting :)

  5. @b9AcE @fedora @kde

    Also apparmor is used instead of selinux. And it was maintained afaik from only one person #busfactor But besides these interesting :)

  6. Hi @signalapp, can we talk about the #BusFactor following today's outage of AWS? How comes Signal communications go down when Armagezzon goes down?

  7. Hi @signalapp, can we talk about the #BusFactor following today's outage of AWS? How comes Signal communications go down when Armagezzon goes down?

  8. ☝️ Surprise! Yet another Amazon engineer believes they're uniquely qualified to solve AI's problems while simultaneously ignoring the all-important Bus Factor 🚍💥. Because who needs a backup plan when you've got infinite hubris? 🤷‍♂️
    mindflash.org/coding/ai/ai-and #AmazonEngineer #AIHubris #BusFactor #TechIrony #BackupPlan #HackerNews #ngated

  9. ☝️ Surprise! Yet another Amazon engineer believes they're uniquely qualified to solve AI's problems while simultaneously ignoring the all-important Bus Factor 🚍💥. Because who needs a backup plan when you've got infinite hubris? 🤷‍♂️
    mindflash.org/coding/ai/ai-and #AmazonEngineer #AIHubris #BusFactor #TechIrony #BackupPlan #HackerNews #ngated

  10. 💯th citation for our work on "Assessing the bus factor of git repositories"

    A good related research question today would be whether #bots / #agents reduce the bus factor risk compared to when humans were the only contributors to a project.

    #SANER15 #busfactor #git #research #opensource #oss #msr

    scholar.google.es/citations?vi

  11. Reading about Google keeping their long tradition of discontinuing products/services, often after just a few years[1]. On the other hand, the minimal "bus factor"[2] of my open source offerings is one of the stated reasons for people to not use them, even though the vast majority of the 200+ thi.ng/ libraries & tools has been actively maintained for much longer than many Google projects (99% by this single person)... Even many of my older projects which are defunkt by now have had an active period which outlasted many Google services, and — crucially — they're are stable, still available and can still be used now (e.g. my Java library collection developed between 2005-2013 still has regular users)...

    Maybe internal politics, re-orgs and layoffs in BigTech are an equal/bigger risk factor for users (aside from other differences in design philosophy and resulting coupling and tech debt, e.g. massive all-in frameworks vs. lightweight composable pick-n-mix toolkits)? 🤔

    [1] killedbygoogle.com/
    [2] en.wikipedia.org/wiki/Bus_fact

    #OpenSource #BusFactor #Maintenance

  12. Reading about Google keeping their long tradition of discontinuing products/services, often after just a few years[1]. On the other hand, the minimal "bus factor"[2] of my open source offerings is one of the stated reasons for people to not use them, even though the vast majority of the 200+ thi.ng/ libraries & tools has been actively maintained for much longer than many Google projects (99% by this single person)... Even many of my older projects which are defunkt by now have had an active period which outlasted many Google services, and — crucially — they're are stable, still available and can still be used now (e.g. my Java library collection developed between 2005-2013 still has regular users)...

    Maybe internal politics, re-orgs and layoffs in BigTech are an equal/bigger risk factor for users (aside from other differences in design philosophy and resulting coupling and tech debt, e.g. massive all-in frameworks vs. lightweight composable pick-n-mix toolkits)? 🤔

    [1] killedbygoogle.com/
    [2] en.wikipedia.org/wiki/Bus_fact

    #OpenSource #BusFactor #Maintenance

  13. Please share with your colleagues:
    Asking all US-based scientists:
    Are there repositories of #OpenAccess papers etc. pp. that need mirrored?
    (I'm proud #GuerillaOpenAccess, but not currently trying to do an Aaron Swartz #RIP 😢)

    You've got research to safeguard?
    Consider uploading to zenodo.org (run by CERN, well established, trustworthy, you can private your uploads)

    To organize: matrix.to/#/#safeguarding-rese
    (Everyone welcome! #BusFactor)

    @academicchatter @academicsunite

  14. Please share with your colleagues:
    Asking all US-based scientists:
    Are there repositories of #OpenAccess papers etc. pp. that need mirrored?
    (I'm proud #GuerillaOpenAccess, but not currently trying to do an Aaron Swartz #RIP 😢)

    You've got research to safeguard?
    Consider uploading to zenodo.org (run by CERN, well established, trustworthy, you can private your uploads)

    To organize: matrix.to/#/#safeguarding-rese
    (Everyone welcome! #BusFactor)

    @academicchatter @academicsunite

  15. stop using niche #linux distributions already p l e a s e.

    just use #debian, #ubuntu, #fedora, or even #opensuse. these titanic collective efforts are so much better at creating a good, reliable, secure, and accessible computing environment than today's Distro Of The Week with a #BusFactor of one (1).

    thank you.

  16. stop using niche #linux distributions already p l e a s e.

    just use #debian, #ubuntu, #fedora, or even #opensuse. these titanic collective efforts are so much better at creating a good, reliable, secure, and accessible computing environment than today's Distro Of The Week with a #BusFactor of one (1).

    thank you.

  17. @tlaurion @jrf_nl @opencollective Listening to the keynote, I wrote for communal clarity in case of #maintainer #death and how to continue maintenance of my #FOSS #projects.

    github.com/niccokunzmann/case-

    Really, I wonder how to reach out to increase the #busFactor of my projects. But in case this has not happened tomorrow, there is my #software #will :)

    My intention is also to flag up the issues we face as a community.

  18. @vaurora: In this case it was rather "not enough people involved" istead of "too many involved": See #busfactor and xkcd.com/2347 #xkcd2347

    This was only possible because the original maintainer did that work alone and seems to have been close to a #burnout and urgently needed someone to step in. So it was easy to get the co-maintainer position without long-time #trust being involved.

    #JiaT75 #xzorcist #xz #FLOSS

  19. @vaurora: In this case it was rather "not enough people involved" istead of "too many involved": See #busfactor and xkcd.com/2347 #xkcd2347

    This was only possible because the original maintainer did that work alone and seems to have been close to a #burnout and urgently needed someone to step in. So it was easy to get the co-maintainer position without long-time #trust being involved.

    #JiaT75 #xzorcist #xz #FLOSS

  20. Funny... But lets not forget the real unprofessional problem is for a company to rely on a #BusFactor of 1.

    (see en.wikipedia.org/wiki/Bus_fact)

  21. Funny... But lets not forget the real unprofessional problem is for a company to rely on a #BusFactor of 1.

    (see en.wikipedia.org/wiki/Bus_fact)

  22. @dansup as far as I know, you do almost all of the development on pixelfed yourself. Would this be an opportunity to move to a maintainer team?

    #busfactor

  23. @dansup as far as I know, you do almost all of the development on pixelfed yourself. Would this be an opportunity to move to a maintainer team?

    #busfactor

  24. @johnm I have similar concerns about #CondaForge #BusFactor again from the perspective of a minor contributor to/of a few recipes.

  25. @johnm I have similar concerns about #CondaForge #BusFactor again from the perspective of a minor contributor to/of a few recipes.

  26. 🚌 Facteur de bus : évitez de mettre tous vos œufs dans le même panier

    J'ai discuté avec quelqu'un dont le CTO était la seule personne à intervenir sur les parties critiques de leur application. Cela m’a rappelé le concept du "Bus Factor."

    #BusFactor #Collaboration #SharingKnowledge #DevTeam

    J'explique 🧵👇[1/4]

  27. 🔴New issue of The Optimist Engineer newsletter @optimistengineer

    The Bus Factor represents the risk of having all the knowledge, that is critical for your business (either a company or a dev team), in one single person or a small set of people. In today's issue, I share my experience about this and some advice to avoid this happening

    open.substack.com/pub/optimist

    #optimistengineer #experience #growth #share #engineer #softwareengineering #softwaredevelopment #startup #busfactor #learnings #techlead

  28. 🔴New issue of The Optimist Engineer newsletter @optimistengineer

    The Bus Factor represents the risk of having all the knowledge, that is critical for your business (either a company or a dev team), in one single person or a small set of people. In today's issue, I share my experience about this and some advice to avoid this happening

    open.substack.com/pub/optimist

    #optimistengineer #experience #growth #share #engineer #softwareengineering #softwaredevelopment #startup #busfactor #learnings #techlead

  29. A few of my bigger projects have additional contributors, but outside of @dedication_bot it's a 1.

    One thing I'm doing for my personal site and @botwiki is that articles are automatically backed up to web.archive.org, plus most of my work is open-sourced, so at least it should be possible to resurrect most of it.

    #opensource #SideProjects #BusFactor

  30. A few of my bigger projects have additional contributors, but outside of @dedication_bot it's a 1.

    One thing I'm doing for my personal site and @botwiki is that articles are automatically backed up to web.archive.org, plus most of my work is open-sourced, so at least it should be possible to resurrect most of it.

    #opensource #SideProjects #BusFactor

  31. @ij Possibly side-tracking, but I'm curious: do you have, plan to have or consider having a team of moderators? My impression (as a user) is that doing both the admin job and the moderation job is quite time-consuming. Also, a risky thing to have a #BusFactor of 1.

  32. @ij Possibly side-tracking, but I'm curious: do you have, plan to have or consider having a team of moderators? My impression (as a user) is that doing both the admin job and the moderation job is quite time-consuming. Also, a risky thing to have a #BusFactor of 1.

  33. @jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.

    Lessons learned, however, at social.antefriguserat.de/index.

    Related subreddit: old.reddit.com/r/plexodus/

    I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).

    • Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.

    • Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.

    • Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.

    • Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.

    • #SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: social.antefriguserat.de/index

    • Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.

    • In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)

    • There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.

    • People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.

    There's more I could write, this is probably a good start.

    #TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms

  34. @jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.

    Lessons learned, however, at social.antefriguserat.de/index.

    Related subreddit: old.reddit.com/r/plexodus/

    I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).

    • Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.

    • Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.

    • Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.

    • Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.

    • #SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: social.antefriguserat.de/index

    • Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.

    • In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)

    • There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.

    • People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.

    There's more I could write, this is probably a good start.

    #TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms

  35. Bus factor
    Comment se préparer aux changements de gouvernance dans ses projets, ou juste éviter de tout perdre le jour où une seule personne dans notre équipe se fait écraser par un bus ?

    ça ne vous aura pas échappé, nous sommes tous mortels (sauf Chuck Norris). Du coup il est important de se poser quelques questions sur notre avenir, surtout dans une période de pandémie où la mort frappe plus sou
    cipherbliss.com/bus-factor/
    #logicielslibres #busfactor #pérennité #projet