April 14, 2026
Parentheses and Pitchforks
Repository Pattern with Hygienic Macros in Scheme – Lisp
Code-that-writes-code splits app from database—and the comments riot
TLDR: A developer used Scheme macros to cleanly separate app code from the database with a “repository” layer. Commenters split between praising the tidy, test-friendly design and calling it needless indirection, launching interface jokes, parenthesis memes, and pleas for real-world benchmarks to prove it’s worth the hype.
Scheme dev drops a tiny pair of “code that writes code” macros to separate app logic from the database, and the comments go thermonuclear. Fans cheer the clean split: no more tangled data code, easier testing, and a cute mini language for defining methods. Skeptics smell theater, calling it “wrapping a function in a function with prestige parentheses.”
The approach uses hygienic macros—safe templates that generate functions—to build a “repository,” basically a polite middleman between your app and SQLite. One macro makes easy, name-based record constructors; the other forwards calls to whatever data backend you plug in. Supporters say it’s small, readable, and practical, proof that functional programming can play nice with real apps. Detractors argue it’s just indirection: “you could inline this and nobody would cry,” and worry future teammates will flee from mysterious macro magic.
Then the memes roll in. Parentheses jokes flood the thread hard. An ex-Java crowd insists this simply rebuilds interfaces, now with Lisp flair. Language tribes trade “we did it first” jabs. One joker posts a repo diagram captioned “Now hiring: Macro Whisperer.” Another begs for benchmarks, chanting “show me the speed.” The only consensus? The demo looks slick—and the debate looks even better.
Key Points
- •The article implements the Repository Pattern in Scheme to decouple the data layer from controllers using hygienic macros.
- •Two macros are introduced: define-record-with-kw (SRFI-9 record + keyword constructor + auto-exports) and define-repo-method (arity-flexible repository method).
- •An eDSL is formed where repository methods delegate to repository accessors, reducing boilerplate and supporting keyword/optional arguments.
- •A “projects” repository example defines a repository record and a get-projects method with a descriptive docstring.
- •A concrete SQLite-backed implementation using Artanis is provided in a separate module, exporting make-sqlite-project-repository and remaining decoupled from domain logic.