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.
Links mentioned during the podcast:
I'm a technical writer / API doc specialist based in the Seattle area. In this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, visual communication, information architecture, writing techniques, plain language, tech comm careers, and more. Check out simplifying complexity and API documentation for some deep dives into these topics. If you're a technical writer and want to keep on top of the latest trends in the field, be sure to subscribe to email updates. You can also learn more about me or contact me.