You know this by now: AI will not build you anything useful if you don't know what you want.
It's cool, it's amazing, it's the next jump. How many instances are out there of LLMs messing up production, deleting crucial configurations, or plain misunderstanding the task.
People keep typing and the jobs keep changing. The roles are evolving into something else. This is true for tech writers as much as programmers.
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 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.