Technical Documentation
View All Tags
AI isn't coming for your job.
It's coming for the tasks that make up your job.
This isn’t a new story.
If you’ve ever read a James Bond novel, you’ll remember the typing pool. Highly trained typists who could type super-fast and send confidential reports to the four corners of the world to stymie the latest villain. You don’t see too many typing tools any more. When the typewriter arrived, the typing pool as we knew vanished.
When we're in the role of a 'reader' we tend to skim over the 'happy path' in user guides and other types of documentation. Quite often we only turn to documentation when lost, confused, or uncertain. For instance, someone changed a parameter setting and we can't figure out how to fix it. So, we crack open the docs, search, and go hunting for the answer. But where is it? What should I search for?
I mention this as last week, I started to listen to Roger Penrose's 'The Emperor's New Mind' and came across a section where he discusses 'truth tables' in the context of classical logic and computation, and also their limitations in terms of understanding 'human' consciousness.
On the way home from my walk, I began to think if I could apply this concept to technical documentation.