Pie doesn't need to be original unless you claim it so
Programmers are debating whether side projects need to be novel or useful to others, using a “peach pie” metaphor to question expectations around originality in software. Many argue that, like baking or playing music, recreating existing tools is valid for learning, enjoyment, or craftsmanship, even if no one else adopts the result. Others counter that, because software is infinitely copyable and users invest time to switch, it’s reasonable—especially in public forums or commercial contexts—to ask how a new tool differs from what already exists.
Analogy: Pie vs. Software
- Many argue the pie analogy breaks down: pies are physical, consumable, geographically constrained, degrade over time, and are rival goods; software is infinitely copyable, non-rival, and globally accessible.
- Several tweaks are proposed: software is more like a pie recipe (or chair design) than a pie; others think it’s closer to a shovel or chair (a durable tool) than to food or art.
- Some note that analogies to music performance, painting, or blacksmithing may work better for recreational programming than food analogies.
Originality vs. Utility
- One camp says: because software is easily duplicated, users reasonably ask “How is this different or better?” before investing time. Utility and novelty justify attention.
- Another view: insisting on originality for every side project is misplaced; many things exist primarily for fun, learning, or craftsmanship. Execution quality can be a differentiator even if the idea isn’t new.
- There is debate about whether reimplementations (e.g., another TODO app, JS framework, or office suite) have value beyond the creator’s learning or portfolio.
Learning, Craft, and Non-Utility Value
- Multiple comments stress that copying/replicating (simple apps, basic recipes, garden tools) is how people build mastery before doing “state-of-the-art” work.
- Others emphasize intrinsic joy and personal expression: like playing classical pieces, painting, or doing covers, originality isn’t always the main point.
Sharing Side Projects and HN Culture
- Some say that posting on Hacker News implicitly invites evaluation against existing solutions; submitters should clarify what’s different to respect readers’ attention.
- Others criticize harsh “what does this offer over X?” reactions, especially toward free, learning-oriented projects, as entitled or unempathetic.
- There’s recognition that HN’s novelty-seeking, dopamine-driven dynamic biases discussions toward originality and can undervalue solid but derivative work.
Feedback, Friendships, and Social Norms
- Disagreement over how friends “should” respond: some expect honest, even blunt feedback about unoriginality; others see that as emotionally tone-deaf or mean unless invited.
- Several note the difference between supporting someone’s growth (asking about their process or goals) vs. demanding market-level differentiation for a hobby project.