ARTICLE · How software is shaped
Worse is better
A modest system people can install, understand, and improve can travel further than an elegant system they cannot adopt.
Worse is better
YouTube stays disconnected until you choose to load this player. Loading connects to Google/YouTube, which receives your IP address and may use cookies or browser storage.
“Worse is better” is deliberately uncomfortable. The phrase invites you to notice that software succeeds inside a world of limited time, unfamiliar machines, imperfect documentation, and people who need something useful today. A design can be beautiful on paper and still demand too much from everyone who tries to use it.
The useful tension is between completeness and adoption. A small tool with a predictable interface may spread, gather feedback, and improve. A more comprehensive competitor may remain unfinished or require a specialist to get started.
Choose what is allowed to be smaller#
For a guild calendar, a first version might support one timezone and a single reminder channel. That is a narrower product. Silently sending reminders at the wrong time is a broken promise. Shipping less scope and shipping unreliable behavior are different decisions.
Write down the property you are optimizing: ease of installation, a small implementation, compatibility, or a complete feature set. Then name the cost you are accepting. The discussion becomes useful when the tradeoff is explicit enough that someone could disagree with it.
This also changes how you read mature software. Rough edges may reflect constraints, compatibility commitments, or a deliberate adoption strategy. They are worth investigating before imitating. Paired with KISS and YAGNI, the idea gives you three questions: can we understand it, do we need it now, and can people actually use it?
See also