An Engineer's Field Guide to Great Technical Writing

<p><a href="https://docsfordevelopers.com/"><i>Docs for Devs: An Engineer’s Field Guide to Technical Writing</i></a> can be found here.</p><p>Jared worked as a technical writer at Google for more than 14 years and recently transitioned to Waymo, the self-driving car company spun out under the Alphabet umbrella. You can find him on <a href="https://twitter.com/jaredbhatti">Twitter</a> and <a href="https://www.linkedin.com/in/jaredbhatti/">LinkedIn</a>.</p><p>Zachary has been a technical writer at GitHub and the Linux Foundation, and now works as a staff technical writer at Stripe. You can find all his online accounts at his <a href="https://corleissen.com/">website</a>.</p><p>Interested in exploring approaches for collaboration and knowledge management on engineering teams? Why not try a tool developers already turn to regularly? Check out <a href="https://stackoverflow.co/teams/">Stack Overflow for Teams</a>, used by Microsoft, Bloomberg, and many others.</p><p>Tired of security bottlenecks? Today’s episode is sponsored by Snyk,  a developer security platform that automatically scans your code, dependencies, containers, and cloud configs — finding and fixing vulnerabilities in real time, from the tools and workflows you already use. Create your free account at <a href="https://snyk.io/?utm_campaign=Dev-Sec-BRD-2022&utm_medium=Paid-Podcast&utm_source=StackOverFlow&utm_content=developer-loved-security-trusted-homepage">snyk.co/stackoverflow</a>.</p>