Whatever can be, will be.

You may think of a technical writer as the person who produces documentation. But the role has changed. It now sits at the center of design thinking, context protocols, content strategy, user journeys, AI-augmented authoring, automated workflows, docs as a product, and communication between humans and machines.

If you still treat technical writing as a support function, you will miss where product value now lives.

Language is no longer a layer on top of software. It shapes how software behaves. In AI-native systems, language is part of the system.

You do not need a better writer. You need someone who designs how knowledge flows across your organization and your product.

I've always pondered our definition of human intelligence. Civilization even. A definition that I like is — our ability to manipulate our environment.

Tech keeps you capable. Art keeps you sane.

I tried this insert product so you don't have to.

There's a myriad of AI tool reviews out there. Kind of reminds me of the whole microservices hype. I swear, for about two years this buzzword was in every single meeting I attended. Now it's "AI-powered" everything. AI-powered toaster. AI-powered calendar. AI-powered AI.

So what's the point in writing this?

Adam Savage once said that as a hobbyist, you should buy the cheapest tools you can find and use them until they break. When they break — and they will — you'll know two things: you're serious about the craft, and you now know exactly what you need. Then you buy the best tools you can afford.

This translates beautifully to technical writing.

Something weird is happening in tech.

The people who build the apps, configure the notifications, and automate everything they can — are the same people turning it all off.

What are the most important aspects of being a technical writer?

Sometimes, you just need to write it down.