01.04 — Citations and claimed influences#
The references cited in the Holy Book aren’t neutral — they set Ocarina’s theoretical frame. We cut them by axis here, then offer the overall reading.
Technical axis — Functional programming, types, languages#
| Influence | Origin | Relation to Ocarina |
|---|
| Railway Oriented Programming (ROP) | Scott Wlaschin (F#), a well-known pattern in functional programming | The heart of the framework. Result[T] = Ok[T] | Fail, short-circuit, fluent builder. See ../02-ocarina/03-railway/. |
| λ-calculus (1930) | Alonzo Church | Cited as the invention that makes possible the “clean formalization” Ocarina pursues: “What has been on our minds since the 1930s, since the invention of λ-calculus, is finally scalable to the degree we always wanted it to be.” |
| McCulloch & Pitts (1943) | First formalization of the artificial neuron | Cited as a reminder that the real progress in AI is old and continuous, against the recent hype. |
| Python type system (PEP 695) | PEP 695 (Python 3.12+) | Prerequisite for the generic parametric typing that structures Ocarina (TestSuite[Driver], Result[T], etc.). See ../03-functional/06-pep-695-generics.md. |
Cultural axis — Anti-narcissism, simplicity, KISS done right#
| Influence | Citation | Why |
|---|
| Terry Davis (“the smartest programmer that’s ever lived”) | “An idiot admires complexity, a genius admires simplicity, a physicist tries to make it simple…” | Anti–ostentatious complexity argument; cornerstone of the “First feedbacks” chapter. |
| Lao-Tzu | “To attain knowledge, add things every day. To attain wisdom, remove things every day.” | A subtractive method: what remains after elimination. |
| Antoine de Saint-Exupéry | “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” | Western restatement of the previous one. Closes the “First scenarios” chapter. |
| Alan Watts | “Muddy water is best cleared by leaving it alone.” | Cited at the end of the “First jutsus” chapter: legitimizes a design that refuses certain features (reactivity, async). Legitimizes stepping out of the “geek tricks” ecosystem. |
| Rainer Maria Rilke | “Live the questions now. Perhaps then, someday far in the future, you will gradually, without even noticing it, live your way into the answer.” | Closes the “First steps” chapter. Stance toward practice: mastery comes from use. |
| Marcel Proust | “For the writer as well as for the painter, style is not a question of technique, but of vision.” | Closes the “Extensibility” chapter. Justifies the refusal to impose a DSL: vision (POMs + actions) trumps technique (a format). |
Political axis — Code, sovereignty, anti–startup nation#
| Influence | Origin | Relation to Ocarina |
|---|
| Code is Law | Lawrence Lessig (1999), reclaimed by Ethereum (2015) as a positive ideal | Cited as the stance against “democratic governance of code”. The project claims it: “Once again, with AI, that sorely missing digital body, let us scream it, as loud as we screamed ‘HACK THE PLANET’ back in ‘99: CODE IS LAW.” |
| DHH — I won’t let you pay me for my open source | David Heinemeier Hansson, personal blog | Cited to legitimize refusing unaligned contributions (“Fuck You” references DHH’s famous slide). |
| Paul Graham — Haters | PG essay (paulgraham.com/fh.html) | Grounds the decision to “never waste time arguing when it isn’t worth it”. |
| Yegor Bugayenko — Prompt | The quote “Retry flaky blocks.” | Grounds the transient_errors + linear retry policy (TestFlow). Read also: Angry Tests. |
| The DAO hack (2016) | Hack of The DAO on Ethereum | Cited to point out that it was bugs (“damned bugs, because of damned devs”) that set Code is Law back, hence the importance of typing and rigor. |
| Lee Robinson (ex-Vercel) | December 2025: Cursor replacing Sanity with Markdown files + AI | Backs the “return to raw data”. |
| Cluely (Roy Lee) | Cited as an illustration of entrepreneurial bullshit to avoid | Explicit contrast with the Ocarina philosophy. |
Identity / underground axis#
| Influence | Origin |
|---|
| LulzSec — “In the Lulzboat, salute, bitch, and show some respect.” | AntiSec (YTCracker, 2011) |
| “We Can Do All What You Can’t Do” | YogyaCarderLink |
| YTCracker — Robots Will Definitely Take Your Job | SoundCloud link, background music of the “First feedbacks” chapter |
| “HACK THE PLANET” (1999) | Emblematic slogan of the 1990s hacker scene + AntiSec (YTCracker, 2011) |
| Zone-H | Historic web defacement archive |
| r/unixporn, r/AntiTaff | Subreddits |
| Influence | Origin | Relation to Ocarina |
|---|
| Claude Code | Anthropic | Reference tooling for the AI project (ocarina-with-ai-example). Cited several times as the “bridge” replacing DSLs. |
| IntelliCode (2018) | Microsoft | Cited as a temporal landmark (“we had already tasted it, well before IntelliCode”). |
| R., the silo’s mad scientist | Personal anecdote (a 2013 colleague, a private Emacs AI plugin) | Reminder that generative AI (“15,000 lines to delete to avoid writing 1,000”) existed before the public hype. |
| Prisma, Vercel, Cursor | SaaS ecosystem | Cited as practical cases of an AI-assisted return to raw data. |
Overall coherence#
All these influences converge on three axes:
- Typed raw data as primary material (λ-calculus → ROP → typed Python → AI).
- Sophistication that lands at simplicity as quality metric.
- Sovereignty as political stance.
ROP is the technical embodiment. Turn the failure flow into a typed value (Ok/Fail), not a side effect (a raised exception). The result is both functional and accessible. The Holy Book sums it up:
By design, Ocarina makes itself hard to misuse: the compiler has the final say.
What these influences didn’t bring#
| Absent | Why |
|---|
| No reference to a competing adopted test framework (Cypress, Playwright, Mocha, Jest, RF, Cucumber) | All are mentioned in contrast, never as a source of inspiration. |
| No reference to a “Clean Code” or “SOLID” school | “You. Don’t. Even. Know. What. ‘Clean code’. Actually. IS.” |
| No reference to a DI framework (Spring, Guice, Hilt) | IoC is done via closures — see ../03-functional/02-closures-ioc.md. |
Absence is also a choice.