

I’d argue the two aren’t as different as you make them out to be. Both types of projects want a functional codebase, both have limited developer resources (communities need volunteers, business have a budget limit), and both can benefit greatly from the development process being sped up. Many development practices that are industry standard today started in the open source world (style guides and version control strategy to name two heavy hitters) and there’s been some bleed through from the other direction as well (tool juggernauts like Atlassian having new open source alternatives made directly in response)
No project is immune to bad code, there’s even a lot of bad code out there that was believed to be good at the time, it mostly worked, in retrospect we learn how bad it is, but no one wanted to fix it.
The end goals and proposes are for sure different between community passion projects and corporate financial driven projects. But the way you get there is more or less the same, and that’s the crux of the articles argument: Historically open source and closed source have done the same thing, so why is this one tool usage so wildly different?
That’s kind of the point though, isn’t it?
If I were to post with “Extend the plank!” there’s a near zero chance that even fans of the movie, or even the franchise, I’m thinking of will get the movie right. If I instead say “Who am I to argue with the Captain of the Enterprise” a normie might guess Star Trek, a true nerd and fan of the franchise will peg that instantly as from Star Trek Generations
Edit: That said, there are several lines in this thread that aren’t necessarily only recognizable to fans or people familiar with the movie, but instead just pop culture references.