The Threads That Connect Everything

This book doesn't have chapters in the traditional sense. It has threads - six of them - and they weave through every piece I've written. Understanding these threads won't just help you navigate the book. It'll help you see how my brain works. Which is kind of the whole point.

Why Themes Matter More Than Chapters

Traditional nonfiction books promise linear progression. Start at chapter one, read to the end, you'll understand the thing. That structure never worked for how I think. I don't process information linearly. I process it in parallel - multiple tracks running simultaneously, connecting unexpectedly, building patterns across seemingly unrelated domains.

So instead of forcing my thinking into chapters, I let the natural structure emerge. What I found were six themes that kept appearing across everything I wrote, six threads that tie the whole thing together.

Thread One: The ADHD-AI Parallel

This is the core insight, the one that started everything. The same constraints that make ADHD challenging - limited working memory, attention management overhead, the need for external scaffolding - are structurally equivalent to the constraints in AI systems.

Context windows are working memory. That's not a metaphor. It's structural equivalence. The same strategies I developed over decades to manage my ADHD brain translate directly into patterns for building AI systems. The connection isn't coincidental. Both systems face the same fundamental problem: you can only hold so much at once. Everything else needs architecture.

This thread shows up in the technical deep dives, in the personal stories, in the system designs. It's the lens through which everything else makes sense.

Thread Two: Infrastructure Thinking

Infrastructure isn't just what you build. It's how you think. This thread traces my evolution from "build features, ship products" to "build foundations that make future building easier."

The pattern appears everywhere once you see it. In software architecture: build the data layer before the UI layer. In AI systems: build the context management before the agentic loops. In personal productivity: build the capture system before worrying about organization.

Infrastructure thinking is about playing the infinite game - optimizing for optionality rather than immediate outcomes. It's the difference between building a house and building the tools that let you build houses faster.

Thread Three: Knowledge Graph Architecture

Everything I know lives in a knowledge graph. Not a metaphor - an actual graph database where notes connect to notes, concepts link to examples, and the structure of the data mirrors the structure of my thinking.

This thread covers both the technical implementation and the cognitive philosophy behind it. Why graphs over hierarchies? Because my thinking doesn't fit in folders. Ideas belong to multiple contexts. Connections matter more than categories. The knowledge graph architecture is ADHD brain externalized into software.

And increasingly, it's how I work with AI. The graph isn't just my memory - it's Claude's context. Every conversation pulls relevant nodes, surfaces connections I might have missed, extends my thinking beyond what I could hold alone.

Thread Four: Human-AI Partnership

I don't use AI to replace my thinking. I use it to extend my thinking. This thread explores what genuine partnership between human and AI looks like - not the utopian "AI will solve everything" pitch, not the dystopian "AI will destroy everything" warning, but the practical middle ground where AI becomes a cognitive extension.

This is the human-in-the-loop pattern applied to creative and analytical work. The human provides judgment, context, values. The AI provides processing power, pattern recognition, tireless iteration. Neither is sufficient alone. Together, we're something neither could be separately.

The thread traces concrete examples: writing with Claude as a thinking partner, building systems where AI handles the routine and humans handle the exceptions, designing workflows where handoffs between human and AI feel natural rather than forced.

Thread Five: Learning in Public

I write about things while I'm still figuring them out. This thread is about the practice and philosophy of building in public - sharing work-in-progress, documenting failures alongside successes, letting the learning process be visible.

For someone with ADHD, this pattern serves multiple purposes. The external accountability keeps projects moving. The public commitment makes it harder to abandon things mid-stream. The feedback loop accelerates learning in ways that private practice can't match.

But it's more than productivity hack. Learning in public is a stance toward knowledge. It says: I don't have to be the expert to contribute. I don't have to be finished to be useful. The journey is the product, not just the destination.

Thread Six: Technical Memoir

This entire book is an experiment in a form I'm calling technical memoir - deeply personal writing about deeply technical subjects, where the personal and technical illuminate each other.

Most technical writing strips out the human element. It presents clean solutions to defined problems, as if insight arrived fully formed. Technical memoir puts the mess back in. It shows the false starts, the moments of confusion, the accidents that led to breakthroughs.

Most memoir writing strips out the technical element. It presents emotional narratives without the detailed how. Technical memoir insists that the how matters - that understanding the specific mechanisms, the actual implementation, the precise architecture is part of understanding the experience.

This thread is meta - it's about the form of the book itself. But it's also practical guidance for anyone who wants to write about technical work in ways that feel human.

How the Threads Weave Together

These six threads aren't separate topics. They're different angles on the same underlying reality.

The ADHD-AI parallel (thread one) drives the need for infrastructure thinking (thread two). Infrastructure thinking leads to knowledge graph architecture (thread three). The knowledge graph enables human-AI partnership (thread four). Working with AI in public becomes learning in public (thread five). And documenting all of this requires technical memoir (thread six).

Start with any thread, follow where it leads, and you'll end up touching all the others. That's not a design choice I made. It's the natural structure that emerged. The threads are real - they existed in my thinking before I named them.

Finding Your Entry Point

You don't need to understand all six threads to get value from this book. Pick the one that resonates most with where you are right now.

If you're struggling with ADHD and curious about AI: start with thread one.

If you're building systems and want to think more architecturally: start with thread two.

If you're drowning in information and want a better way to think: start with thread three.

If you're using AI tools and want to use them better: start with thread four.

If you're building in public or considering it: start with thread five.

If you're trying to write about technical work: start with thread six.

Every thread connects to every other thread. Once you're in, you'll find your own path through.

Related

For specific reading paths tailored to different audiences, see Find Your Path Through This Book. For the deep dive on the core ADHD-AI parallel, see ADHD Brain Parallels with AI Agents.