Reading a long-form piece on, say, the Peloponnesian War. Thucydides gets mentioned as a primary source. I half-know who he is — historian, Athenian, that's about it — but not enough to understand why the author is citing him specifically over Herodotus. Opening a new tab means I lose the sentence I was in. Skipping it means I read shallower than the text deserves. rabbitholes is a Chrome extensio
The Autonomous Paradox In 2026, we’ve moved past simple chatbots. We are building Production-Grade RAG pipelines and autonomous agents that can plan, execute, and iterate. But as an architect, I’ve noticed a glaring hole in our "Agentic" future: Identity Sprawl. We are giving agents non-human identities (NHI) with "Full Admin" permissions just to ensure the RAG works smoothly. We are effectively
This is the third post in my Google Cloud Next '26 (Las Vegas) recap series. You can find the previous posts here 👇 Part 1: [Google Cloud Next '26 Recap #1] Hands-On with the Agentic Hack Zone Part 2: [Google Cloud Next '26 Recap #2] Three Unique Booths I Tried at the EXPO In Parts 1 and 2, I covered my experiences on the EXPO floor. This time, I'd like to switch gears and share one of the se
An opinionated list of Python frameworks, libraries, tools, and resources
This article was originally published on https://forg.to/articles/how-to-stop-hitting-claude-usage-limits *You're Paying for Claude. You're Also Wasting Most of It. I used to hit my usage limit by 2pm every day. Not because I was doing too much work. Because I had no idea how Claude actually charges you. Once I understood the real mechanic, everything changed. I now hit my limit maybe once a mont
The Idea After deciding to build an iOS app using AI, the first thing I set out to create was a metronome app designed for dark stage environments. Back in college, I played drums — and while that was a while ago, there weren’t many metronome apps that felt both clean and professional. (Turns out, that’s still true today.) That’s what led me to the idea: a simple, black-and-white metronome where
TL;DR — Superpowers and Compound Engineering aren't competitors. They're optimised for different worlds. Superpowers is gold for mature codebases with established methodology (TDD shops, large legacy systems, teams enforcing standards). Compound Engineering is gold for early-stage products where one person owns a feature end-to-end. Pick by what your codebase looks like, not by which README sounds
Claude Code is powerful. Without structure around it, every session starts cold, plans live in chat history, and the spec you cared about is buried in a thread you will never re-read. I built Arness because I got tired of two things at once: the ad-hoc-prompting ceiling, and the ceremony every framework adds when it tries to fix it. It is an open-source Claude Code plugin marketplace, and you driv