~/blog/how

Why Rust powers 90% of this system

Almost everything you see here runs on Rust.

the engine

The server, routing, caching, security, analytics and content rendering all live inside a single compiled Rust binary built with Actix Web, SQLite and Tera — the same binary that serves the portfolio you reached this page from.

Posts and view analytics live in one SQLite file beside the binary and images on disk, while Rust does the real work: request processing, memory caching, indexing, SEO generation, rate limiting and observability. The result is a tight, deterministic engine instead of a maze of services.

release binary

15 MB

lto fat, one codegen unit, stripped

debug build

213 MB

with symbols

the pipeline

Content creation has its own twist. Meet Ø (Oxygen / O2) — a custom RAG model built to draft articles in my voice and thinking style. Shell scripts take a raw idea, activate the model locally, and produce a draft that feeds straight into the Rust publishing pipeline. Every article is still revised by hand, but the heavy creative lifting starts there.

store

SQLite

posts, visits, route views

engine

Rust

render, cache, index, rate limit, serve

draft

Ø Oxygen

local RAG model, run from a shell script

Idea → shell script → Ø drafts → Rust stores, processes, caches and serves it.

Language breakdown of the repository, with Rust the large majority
Discounting config files, annotations, versioning and venv files, Rust is close to 90% of the repository.
the philosophy

If a problem is deterministic, why use a non-deterministic language?

Everything ultimately runs on a deterministic computer. When the foundation is deterministic too, the system becomes predictable, debuggable and extremely fast.

what it produced

2

weeks to build

4

days generating

~30

minutes per post

2028

scheduled through

I designed and built this system — backend, content pipeline and AI integration — starting with only prior experience in web apps. To validate it, I pushed it to its limit: Ø generated and iteratively refined a content pipeline scheduled all the way through October 2028.

None of it ran on high-end infrastructure. The whole pipeline ran on a modest local machine, turning constrained resources into a long-term content engine.

No bloated "AI platform" and no orchestration circus — scripts, a model, and a fast backend. Most modern complex stacks do not actually do more than this; they distribute the same logic across dozens of tools.

in practice

This is not "AI-generated content". It is a system that amplifies structured thinking into consistent, long-term output — and every article that ships has been revised by hand.