Building a Body of Work (Not a Feed)

Jan 1
4 min read

Updated: 5 days ago

Overview

Some people don’t have a single, clean lane.

They read widely. They stay curious across domains. They move between physical practice and abstract thinking. Over time, they start writing — not to build an audience, but to keep track of what they’re learning before it disappears.

For a while, this works.

Then something subtle breaks.

Pieces accumulate, but they don’t quite add up. Context fades. Definitions drift. Earlier work stops informing later work. Writing becomes episodic — thoughtful, but disconnected. What looked like a body of work slowly turns into a feed.

This essay is about a different approach.

It’s about how to build coherence over time when your interests don’t stay in one place — not by narrowing them, but by introducing enough structure to let them coexist without collapsing into opinion, branding, or content.

What follows is not a framework or productivity workflow. It’s a description of a constraint — and what becomes possible once that constraint is taken seriously.

Part I: Why Wide Interests Decay into Blogs

Most people with broad interests don’t struggle to start writing.

They struggle to keep their writing coherent over time.

Early on, everything feels connected. Ideas cross-pollinate naturally. Patterns are obvious.

But without structure, that coherence doesn’t survive contact with time.

What usually happens instead:

Each piece is written in isolation
Context is reintroduced inconsistently
Definitions subtly change
Prior work is forgotten or contradicted
Writing becomes point-of-view driven rather than cumulative

This is how thoughtful projects quietly turn into “personal blogs” — not because the thinking gets worse, but because nothing exists to hold it together.

The cost isn’t visibility. It’s continuity.

You begin to lose the ability to build on yourself.

The problem isn’t motivation or discipline. It isn’t a lack of ideas.

It’s the absence of an internal system that allows ideas to accumulate instead of resetting every time something new is written.

Part II: The False Solutions

Modern writing culture offers familiar responses to this problem. They don’t really solve it.

Productivity systems optimize throughput, not coherence. They treat writing as a task stream rather than a long-horizon process.

Content calendars enforce regularity but not integration. They reward consistency at the expense of depth.

Branding and niche selection solve fragmentation by narrowing scope — often at the cost of intellectual honesty.

“Second Brain” culture frequently confuses storage with thinking. Information is captured, but not structured in a way that supports synthesis over time.

These solutions optimize for output.

The problem is structural integrity.

Part III: Writing as a System Under Load

A more realistic way to think about writing is the way engineers think about systems.

You don’t fully understand a complex system before you use it. You interact with it. You test it. You reference documentation when something breaks or matters. Understanding emerges through use, not prior mastery.

The same applies to thinking.

In this model:

Use precedes mastery
Reference is not cheating
Understanding is provisional
Writing is downstream of accumulation

Reference manuals aren’t read cover to cover — they’re consulted. Release notes aren’t memorized — they’re checked when behavior changes. Owner’s manuals aren’t studied — they’re opened when you need to locate the air filter.

This isn’t laziness.

It’s how competent people actually operate.

Applied to writing, this implies something simple but under-acknowledged:

You need a runtime environment for ideas, not just drafts and inspiration.

That environment must:

Preserve context
Stabilize terminology
Allow cross-domain linkage
Prevent drift and quiet contradiction
Support long time horizons

When that structure exists, writing becomes a result, not a performance.

Part IV: From Constraint to Practice

One way to implement this approach is through a linked-note system that treats notes as durable, reusable components rather than stepping stones to drafts. In academic contexts, this is often associated with the Zettelkasten method, described in How to Take Smart Notes by Sönke Ahrens.

Another influence comes from Steven Pressfield’s The War of Art: not for its techniques, but for its posture — treating creative work as professional labor rather than mood-dependent expression.

Together, these suggest a shift:

Writing doesn’t begin with writing.It begins with building a structure capable of holding thought.

Over the last few years, this has meant maintaining a single evolving archive rather than publishing and moving on — treating work as something revised, cross-linked, and stabilized over time instead of replaced by the next post.

One concrete implementation of this approach exists at ShankGym.com .

The subjects vary — endurance events, terrain, geology, astronomy, field research — but the underlying system is the point. The site functions as a live archive under load: concepts are reused, terminology is stabilized, and ideas developed in one domain reappear in another.

It isn’t a content stream.

It’s a working structure.

For readers who care how that machine operates — the note system, the editorial architecture, the linking model — I’ve documented those mechanics in detail there.