Logbot (Nov 15 2024 at 21:00): Logbot (Nov 15 2024 at 21:00):Adam & Jerod discuss the news! Our Merch sale, useful built-in macOS CLI utilities, the slow death of the hyperlink, systematically estimating a project's bus factor, The Browser Company abandoning Arc, the Dead Internet theory & more! :link: https://changelog.com/friends/70
| Ch | Start | Title | Runs |
|---|---|---|---|
| 01 | 00:00 | Let's talk! | 00:38 |
| 02 | 00:38 | Sponsor: Sentry | 02:15 |
| 03 | 02:53 | Rivalries & Friends | 03:02 |
| 04 | 05:55 | That sweet, sweet merch | 05:52 |
| 05 | 11:47 | Going way back (machine) | 01:05 |
| 06 | 12:52 | Useful macOS CLI utilities | 10:35 |
| 07 | 23:27 | The slow death of the hyperlink | 06:15 |
| 08 | 29:42 | Sponsor: Fly.io | 02:23 |
| 09 | 32:05 | Sponsor: Eight Sleep | 02:30 |
| 10 | 34:35 | The Bus / Truck factor | 11:56 |
| 11 | 46:31 | Glass Onion vs Knives Out | 04:03 |
| 12 | 50:33 | Arc is a dead browser walking | 08:35 |
| 13 | 59:08 | Sponsor: AssemblyAI | 01:28 |
| 14 | 1:00:36 | Are you on Bluesky? | 07:33 |
| 15 | 1:08:10 | Dead Internet theory | 07:33 |
| 16 | 1:15:43 | Bye, friends | 00:40 |
| 17 | 1:16:22 | Next week on The Changelog | 01:37 |
Dustin (Nov 16 2024 at 18:41):I’m always a little sad that https://changelog.fm is merely a vanity URL and not the primary
Nabeel S (Nov 17 2024 at 12:38):I'm trying to get people to call the bus factor "the lottery factor" instead.
Matthew Sanabria (Nov 17 2024 at 19:36):Nabeel S said:
I'm trying to get people to call the bus factor "the lottery factor" instead.
I know many people that tried this but it doesn't really catch on with a lot of people. Takes a lot to explain it. Plus winning the lottery doesn't necessarily mean that someone is gone for good. I get the sentiment though.
Ron Waldon-Howe (Nov 17 2024 at 19:43):Negativity definitely gets more human engagement, alas
Don MacKinnon (Nov 18 2024 at 04:08):Regarding the discussion around Bluesky, I've been using it a lot in the past week. Vibe-wise it feels 2014 Twitter like but with much better moderation and tooling baked in. You have far more control over being able to tailor your experience on the platform, plus unlike the others it's built around portability. You can set your handle to be your domain so if down the road you decide to move to another AT protocol platform you're not starting all over. Momentum has definitely picked up, they are at 19 million users now (you had 15 at the time of the recording), they've been adding roughly 1 million users a day for the past several days. I originally signed up back in 2023 but momentum on the platform just picked up since the election.
Daniel Lauzon (Nov 18 2024 at 06:08):Merch!
Lovely new banner...
Great deals.
But shipping costs to Canada are bananas.
Jerod Santo (Nov 18 2024 at 14:36):@Daniel Lauzon DM me your mailing address and I'll see if I can find some cheaper way
Jamie Tanna (Nov 18 2024 at 18:31):Re "the algo" I've got a weird thing with my RSS x-poster on LinkedIn where it never displays the post image, it stopped a while back and pretty sure that's cause they thought I was spamming :sweat_smile:
Jamie Tanna (Nov 18 2024 at 18:37):Parallel is useful! I wrote about it in the past (https://www.jvt.me/posts/2022/04/28/shell-queue/) as it simplified some stuff I was doing considerably
Jamie Tanna (Nov 18 2024 at 18:40):See also https://chaoss.community/kb/metric-contributor-absence-factor/ for an alternative to "bus factor"
Jerod Santo (Nov 18 2024 at 19:13):Naming effort appreciated, but there is a zero percent chance that "Contributor Absence Factor" catches on in any meaningful way...
Another factor that makes "bus factor" sticky as a name is that it's lurid, yet feasible. It just sells the concept of an unexpected, sudden absence of a person really, really well. No further explanation necessary.
I actually think the bigger controversy here was the "truck factor" paper's authors hypothesizing the murder of Python's BDFL by a rival language's mob... :upside_down:
Dustin (Nov 18 2024 at 20:07):CAF score though :thinking:
Dustin (Nov 18 2024 at 20:08):Just jargon-y enough to catch on
Ron Waldon-Howe (Nov 18 2024 at 23:52):It's probably true that most places with coders will also have buses, too
It just occurred to me that maybe the concept of a bus isn't universal, but it's probably more universal than a lottery
Lars Ellingsen (Nov 19 2024 at 04:41):Nabeel S said:
I'm trying to get people to call the bus factor "the lottery factor" instead.
This is how I always refer to it. Just like retro instead of postmortem
Adam Stacoviak (Nov 19 2024 at 06:19):Postmortems and retros are 100% different.
Lars Ellingsen (Nov 19 2024 at 06:58):What's your take Adam? I have an idea in my mind of the difference, but I've seen them used interchangeably so many times.
Nabeel S (Nov 19 2024 at 12:20):I prefer less morbid terminology whenever possible.
Matthew Sanabria (Nov 20 2024 at 06:33):I don't use retro when referring to a postmortem. I didn't even know people did that. I do, however, interchange root cause analysis (RCA) and postmortem.
To me a postmortem is tied to an outage or incident and has a clear goal driven by facts- find out what exactly happened, how it was resolved, and note action items for the future. Two people cannot disagree about what went wrong because there's meant to be a single source of facts for what happened.
A retro can be about anything, does not have a clear goal, and is driven by opinion- people discuss a past experience and share context that'll hopefully make things better for next time. Two people can have different opinions about what can be improved and how to improve it.
Adam Stacoviak (Nov 20 2024 at 14:45):I concur.
Lars Ellingsen (Nov 20 2024 at 15:09):Well said!
Notification Bot (Nov 20 2024 at 19:32):A message was moved here from #general > new episodes by Jerod Santo.
Jerod Santo (Nov 20 2024 at 19:34):@Ed Howard incredibly helpful, thanks! I've driven out to Durham and Chapel Hill from the airport, but not from downtown Raleigh, I guess.
Konrad (Nov 23 2024 at 13:34):Adam Stacoviak said:
Postmortems and retros are 100% different.
I thought a retro refers to a scrum/agile concept of having a meeting in every iteration/sprint to discuss what went well and what went wrong.
A post mortem in my understanding is a investigation and discussion about an incident and what happened in order to trigger it.
Not sure if there are strict definitions about that, but this was my mental model so far :sweat_smile:
Adam Stacoviak (Nov 23 2024 at 15:28):Retro is a review of a sprint or known sustained effort. Typically this is in meeting form with documentation of what each person shared.
Postmortem is a structured analysis of an incident. Typically this is a single person or team activity to examine the incident and often produces an artifact that can be shared with a group to illustrate the incident details.
Adam Stacoviak (Nov 23 2024 at 15:29):They are similar in nature, but not the same.
Philip Durbin (Dec 15 2024 at 13:26):CHAOSS (Community Health Analytics in Open Source Software) recently renamed their Bus Factor metric to Contributor Absence Factor after a lengthy discussion.
Konrad (Dec 15 2024 at 16:04):@Adam Stacoviak probably there is no hard definition, but at least in the context of scrum, it sounds a bit like you are mixing Sprint Retrospective and Sprint Review meetings.
https://scrumguides.org/scrum-guide.html
Sprint Review
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.
The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
Sprint Retrospective
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
Last updated: Jan 06 2025 at 01:13 UTC