11. The Agony and Ecstasy of Maintaining Good Documentation

Code[ish]

Content provided by Salesforce Engineering. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Salesforce Engineering or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

6+ y ago

MP3

Archived series ("Inactive feed" status)

When? This feed was archived on December 12, 2020 08:26 (5y ago). Last successful fetch was on March 02, 2025 02:12 (10M ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

With the explosive growth of people using, and contributing to, open source projects over the last decade, more and more of us are spending their time reading, writing, and understanding documentation.

Heroku's Dev Center is the central hub of documentation for Heroku, covering everything from getting started, to how Heroku works, to extending the platform. It acts as a manual for the entire platform, spanning an enormous number of topics and tools.

Stephen Barlow, lead strategist for Dev Center, joins Heroku designer / developer Charlie Gleason to discuss why good documentation is so important—from some of the common challenges you and your team might face while writing them, to advice for rationalising and improving your documentation workflow.

Tune in to learn why good docs aren't just good—they're great.

Links from this episode

131 episodes

#Programming #Software Development #Tech #Chris Castles