Authoritarianism of Code

Zed Shaw's "Authoritarianism of Code" is a welcome gut check for an open source ecosystem that loves to pat itself on the back for its supposed ivory-tower meritocracy. He connects the dots between absolute technical control and absolute social control — when a single maintainer can veto a merge, rebase your history, or simply "no it doesn't work, bye" you out of a conversation, all the veneer of "community collaboration" evaporates fast. It's an argument that should make everyone with a GitHub username sit up a little straighter. The central tension is that the "Linus style" of blunt, vicious code review is frequently laundered into a form of authenticity or honesty, when at it looks a lot more like plain old personal domination. That's a story as old as computing itself — the priesthood of high priests who gatekeep The One True C99 style. Shaw's observation matters because the stakes are even higher today, when a handful of maintainers control the tools we use to build everything, and a nasty email is often the only recourse for dissent. What makes this piece bite is that it connects the micro to the macro. As Shaw points out, if you can't challenge the person who yells loudest in a GitHub issue thread, you certainly can't challenge them when they have commit permissions and a survival package for a security vulnerability. The culture of code is a culture of power, and pretending otherwise is just about the most "tech bro" thing you can do. This is the kind of lens we need more of in the open source conversation. Read the original full rant at <a href="https://zedshaw.com/blog/2020-10-07-authoritarianism-of-code/" rel="noopener noreferrer">https://zedshaw.com/blog/2020-10-07-authoritarianism-of-code/</a>. It's a sharp, uncomfortable mirror for every maintainer who's ever unleashed a little too much delight in saying "rejected."