Retrieval Augmented Generation In Practice
Chunking, reranking, and the evaluation loop that keeps your RAG pipeline from silently degrading over time.
This is placeholder body copy. In a real post there would be an argument here, built one paragraph at a time, with the kind of small detours that make a technical essay feel like it was written by an actual human.
The repository this page lives in exists to demonstrate behavior of the Next.js router, so the content is intentionally boring. Any similarity to real insight is entirely coincidental, if occasionally welcome.
If you are reading this from a prefetch-triggered hover, congratulations, the link worked. If you are reading it after a full navigation, that also counts, and you have learned something about how caches behave under load.
More posts
Writing a Custom ESLint Rule From Scratch
AST basics, a worked example, and the small codemod that enforced a team convention better than any wiki page.
The Rise of Colocated Configuration
Why the config file nearest to the code it configures tends to win, and what that means for your repo layout.
A Short History of CSS Layout
From floats to grid, a tour of the bad decisions we made together and the better ones we eventually agreed on.