About content, tools, and careers

I've spent most of my career thinking about content as infrastructure. Not as output, but as the thing that supports systems at scale. How people learn, how teams onboard, how products get understood, and how organizations move faster (or don't!).

When content works, it's invisible. When it doesn't, everything feels harder than it should.

This blog explores that idea, along with two related threads: documentation tools keep evolving, and how careers in content evolve alongside them.

Tools matter. I've worked with generations of doc platforms, each promising to make content easier to create and maintain. AI-powered tools are changing that landscape again, raising questions about authorship, quality, ownership, and trust. I'm less interested in hype than in how the tools actually fit into sustainable content systems.

Careers matter too. Content roles are rarely linear. The way we frame our work shapes the opportunities available to us. I'm interested in how people grow in this space, how they avoid narrow definitions, how they position experience as tools shift, and how they build careers that adapt.

If you work in documentation, content strategy, developer experience, or any role where clarity supports scale, I hope something here is useful, or at least helps you see familiar problems from a different angle.

Thanks for reading, and... docs, or it didn't happen!