One Architecture, Many Languages
A practical reference for applying the same four-layer architecture to Node, Java, Swift, Rust, Go, and Ruby.
1461 words
|
7 minutes
|
English
When to Let the Official Tool Win
Don't put every language under mise. One test decides who owns runtime versions: does the language ship a strong, official tool of its own?
991 words
|
5 minutes
|
English
Making mise and uv Agree on Python
uv had installed a Python that mise did not know about. Setting python-preference to only-system restored one clear owner, with a few consequences for existing projects.
1354 words
|
7 minutes
|
English
The Brewfile Compromise: Eventual Consistency for Mac Apps
Not every layer deserves strict declarative management. The app layer is fine with eventual consistency, as long as the drift stays visible.
1155 words
|
6 minutes
|
English
Dotfiles Without .zshrc: ZDOTDIR and chezmoi
Move zsh config out of the home directory with ZDOTDIR, split it into modules, and manage it declaratively with chezmoi so drift becomes visible.
1896 words
|
9 minutes
|
English
I Rebuilt My Mac Around Four Layers
A DFU restore forced me to decide which tool owns each part of my development environment—and how I would rebuild it.
1193 words
|
6 minutes
|
English
How I Learned to Read Swift Function Signatures
When I started learning Swift, I would open Apple’s DocC documentation, see something like this, and skip straight to the examples:
712 words
|
4 minutes
|
English
I Built a Website in Swift, Then Went Back to HTML and CSS
From adding one text style to reconsidering where Swift belongs in a Web stack
1583 words
|
8 minutes
|
English
1
2
3