Keeping Web3 Documentation Useful Across Versions and DomainsA protocol release can change the product faster than its public documentation changes. The new SDK appears in the repository, the marketing page describes a new capability, and a tutorial written for8h ago · 4 min readaeoranker.hashnode.dev
How to Evaluate an AI Tool Before You Pay for ItEvery AI product demo is optimised for the same thirty seconds. Impressive output, clean input, ideal conditions. What it does not show is behaviour at the edges, and the edges are where the tool eith1Aug 24 · 4 min readaeoranker.hashnode.dev
Designing a Corpus: Ownership, Staleness, and the Quarterly ReviewMost RAG write-ups are about retrieval. Chunk sizes, embedding models, rerankers, hybrid search. All of it matters and I've written about it. None of it helps if the corpus underneath is wrong. I buil1Aug 23 · 7 min readaeoranker.hashnode.dev
Instrumenting AI Workflows: What to Log So You Can Tell If It's WorkingMost AI workflows are unmeasured. Not lightly measured unmeasured. They get built, they run, and the only signal anyone has about whether they're worth keeping is a vague sense that things feel fasterAug 20 · 7 min readaeoranker.hashnode.dev
Designing the Boundary Layer: Least Privilege for AI AgentsIn the last piece I audited my stack and found 5 tools that were still authorised to read my email months after I'd cancelled them. The interesting question isn't how that happened it happened becauseAug 19 · 8 min readaeoranker.hashnode.dev
