Monorepo for Aesthetic.Computer
aesthetic.computer
refactor: dead-ends paper voice — first-person consistent, remove "we" constructions
Changed abstract to first-person voice: "I catalog" and "I document" instead of "We", and removed "We argue that" in favor of direct assertion "A project's vestigial features---not its failures---reveal its evolutionary trajectory". Applied VOICE.md guidelines for directness and personal conviction.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
+1
-1
+1
-1
papers/arxiv-dead-ends/dead-ends.tex
+1
-1
papers/arxiv-dead-ends/dead-ends.tex
···
99
99
100
100
\begin{quote}
101
101
\small\noindent\textbf{Abstract.}
102
-
Academic papers about software systems almost exclusively describe what works. This paper describes what went dormant. Over five years of development, \ac{} accumulated 16 vestigial features---code paths that were actively developed, served a purpose for a time, and then went quiet. Like vestigial organs in biology, these features are not dead tissue: some may reactivate if conditions change, some contributed genetic material to the features that survived, and some atrophied because the organism evolved past them. We catalog these features in five categories: \emph{platform branching} (simultaneous development across seven platforms, with five going dormant), \emph{infrastructure experiments} (distributed architectures that consolidated into simpler forms), \emph{monetization attempts} (technically complete systems awaiting market conditions), \emph{single-user tools} (features that served a developmental purpose and were shed), and \emph{premature abstractions} (generic solutions that were replaced by specific ones). For each, we document the rationale for dormancy, the date development diverged, the user activity at the time of diversion, and the potential for reactivation. We argue that a project's vestigial features---not its failures---reveal its evolutionary trajectory, and that dormancy is not death.
102
+
Academic papers about software systems almost exclusively describe what works. This paper describes what went dormant. Over five years of development, \ac{} accumulated 16 vestigial features---code paths that were actively developed, served a purpose for a time, and then went quiet. Like vestigial organs in biology, these features are not dead tissue: some may reactivate if conditions change, some contributed genetic material to the features that survived, and some atrophied because the organism evolved past them. I catalog these features in five categories: \emph{platform branching} (simultaneous development across seven platforms, with five going dormant), \emph{infrastructure experiments} (distributed architectures that consolidated into simpler forms), \emph{monetization attempts} (technically complete systems awaiting market conditions), \emph{single-user tools} (features that served a developmental purpose and were shed), and \emph{premature abstractions} (generic solutions that were replaced by specific ones). For each, I document the rationale for dormancy, the date development diverged, the user activity at the time of diversion, and the potential for reactivation. A project's vestigial features---not its failures---reveal its evolutionary trajectory, and dormancy is not death.
103
103
\end{quote}
104
104
\vspace{0.5em}
105
105
}]