Their tech. Their products. Their stories. In a tech startup, how do you get from an idea on the back of a napkin to a fully functioning product? Code Story is a podcast featuring tech leaders, reflecting the roads they travelled and the products they created. On the show, we interview tech visionaries, digging into the critical moments of what it takes to change an industry, and build (and lead) a team that has your back. Hosted by Noah Labhart, this show is a window into the digital startup world. In their own words, tech veterans share what it feels like to create a world class product, how to recover from critical mistakes, and how to scale your solution to the masses. This podcast is for the tech leader, CTO, CEO, developer, software architect, startup leader, disruptive visionary - or the curious minded individual, who wants to know what a builder goes through in creating world changing technology.
https://codestory.co/
S5 Compiler Recast – Why Should You Write Technical Documentation?
Original episode: https://www.redhat.com/en/compiler-write-technical-documentation
Hey guys, getting close to Thanksgiving in the states. For today, I'm sharing another fantastic episode of the Compiler podcast, from Red Hat. As a reminder Compiler is a show hosted by tech veterans, discussing tech topics - big, strange and small.
On this particular episode - which is episode 8 - the topic of technical documentation is discussed. This is a fitting topic, given that the show is brought to you by Red Hat, which is the largest open source company in the world. The use cases for technical documentation for open source software seem pretty straight forward and obvious - if a developer or user needs to download a free, open source program, they will also need the correlated documentation so they can educate themselves on how to use the program.
In my experience, the need for technical documentation goes way beyond the boundaries of open source. Within the walls of a business, the need to share technical documentation around product architecture, entity relationships, DevOps workflow and even product strategy are absolutely critical in ensuring that everyone is on the same p age to move forward.
At the root, both types of technical documentation have the same goal - to inform the reader on how things should work. This episode was a great discussion on the topic, and I hope you enjoy Episode 8 of the Compiler podcast.
Support this podcast at — https://redcircle.com/code-story/donations
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy