Hey there 👋

Welcome to this installment of Pixel Perfect Picks. Here I'm sharing something that I heard, read, and saw. You can subscribe to this newsletter here. I'm additionally publishing a more extended essay about software development, design, and freelancing every month.

I finished The Strength of the Few this weekend, the second book in the Hierarchy series, and I'm already deep in the rabbit hole trying to survive the wait for book three. If you're in the same spot, this fan theory breakdown is exactly what you need and exactly what you should avoid if you haven't finished the book yet. Proceed with caution. I've watched it twice and I have thoughts. And it obviously has massive spoilers.

Andrej Karpathy published a GitHub gist a few months back describing what he calls an LLM Wiki: instead of doing RAG at query time, you have an LLM incrementally build and maintain a persistent knowledge base as you read. The wiki compounds. The cross-references are already built. Contradictions get flagged. You ask questions and the LLM reads structured, pre-synthesized pages instead of raw document fragments. I set one up myself last week and the analogy he uses is exactly right: Obsidian is the IDE, the LLM is the programmer, the wiki is the codebase. The idea file is here. Copy it into your agent and go.

Christine Røde from The Browser Company wrote about how they designed the AI-generated artifacts inside Dia, their new browser. The interesting part is the decision to deliberately avoid the generic, clean AI aesthetic and go the opposite direction: constrained, typewriter-era ephemera, utilitarian drafts. The morning brief feature pulls in a different public domain painting every day. Small decisions, but they add up to something that actually feels considered. Worth a read.

Keep Creating Awesome Stuff ✌️

If you like these and think someone else might too, please forward it on. They can subscribe to this newsletter right at the top at https://world.hey.com/mrvn. Thank you.

-Marvin