Write the Docs Podcast episode 10: What's going on in our lives as documentarians and product owners
Topics discussed in the podcast:
-
Chris talks about challenges in collaborating with reviewers in efficient ways. Google Docs works great for gathering comments, but it isn’t so good for storing source code in a manageable format. Also, it seems that every company/client has their own preferred toolchain around reviews, and it’s hard to know the best approach to take.
-
Jared talks about the ebbs and flows of managing products in the gambling space, and the challenges around benchmarking, performance testing, and uptime demands for the products he manages, especially during the Melbourne Cup.
-
Tom is excited about the docs-as-code milestone reached at his work, where his team can now build and deploy Jekyll directly from the server through commits to an internal git repo. This publishing efficiency allowed their team to get rid of an old, archaic CMS publishing process that was slowing writers down.
Sponsored
You can view more podcasts at podcast.writethedocs.org. You can subscribe to the podcast using a variety of methods.
Links mentioned during the podcast:
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.
If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.
Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.