[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-jCPtZ8zXTSA-kpzze2zkJ1eDgryFQiV9cmefI_jkNNs":3},{"data":4,"sourceMap":-1},{"info":5,"latest":14,"pinned":145},{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":6,"descriptionText":10,"slug":11,"title":13},"2023-05-23T16:43:21Z","wp-tagcat-technical-writing","9HpbCsT2tq0xwozQfkc4ih","blogTag",null,{"current":12},"technical-writing","technical writing",[15,82,115],{"_id":16,"author":17,"commentCount":29,"comments":30,"excerpt":31,"featureTag":10,"image":32,"publishedAt":36,"slug":37,"sponsored":10,"tags":40,"title":81},"96917cb3-b77d-49bf-a904-b943cf455bbb",[18],{"_id":19,"avatar":20,"name":25,"role":26,"slug":27},"wp-author-295",{"_type":21,"asset":22},"image",{"_ref":23,"_type":24},"image-d670f8093b43e483a52ba692d929578633f70eb5-1024x1024-jpg","reference","Eira May","B2B Editor",{"current":28},"emay",2,true,"Fabrizio Ferri-Benedetti, who spent many years as a technical writer for Splunk and New Relic, joins Ben and Ryan for a conversation about the evolving role of documentation in software development. They explore how documentation can (and should) be integrated with code, the importance of quality control, and the hurdles to maintaining up-to-date documentation. Plus: Why technical writers shouldn’t be afraid of LLMs.",{"_type":21,"asset":33,"attribution":35},{"_ref":34,"_type":24},"image-56c6dab9c7d1b66bc662c5f43ea9573418d94d17-2400x1260-webp","Alexandra Francis","2024-11-26T08:40:00.000Z",{"_type":38,"current":39},"slug","your-docs-are-your-infrastructure",[41,45,49,54,58,65,70,74,76],{"_createdAt":6,"_id":42,"_rev":8,"_type":9,"_updatedAt":6,"slug":43,"title":44},"wp-tagcat-se-tech",{"current":44},"se-tech",{"_createdAt":6,"_id":46,"_rev":8,"_type":9,"_updatedAt":6,"slug":47,"title":48},"wp-tagcat-se-stackoverflow",{"current":48},"se-stackoverflow",{"_createdAt":6,"_id":50,"_rev":8,"_type":9,"_updatedAt":6,"slug":51,"title":53},"wp-tagcat-podcast",{"current":52},"podcast","The Stack Overflow Podcast",{"_createdAt":6,"_id":55,"_rev":8,"_type":9,"_updatedAt":6,"slug":56,"title":57},"wp-tagcat-llm",{"current":57},"llm",{"_createdAt":6,"_id":59,"_rev":60,"_type":9,"_updatedAt":61,"slug":62,"title":64},"wp-tagcat-ai","fpDTFQqIDjNJIbHDKPBGpV","2025-01-30T16:19:01Z",{"current":63},"ai","AI",{"_createdAt":6,"_id":66,"_rev":8,"_type":9,"_updatedAt":6,"slug":67,"title":69},"wp-tagcat-generative-ai",{"current":68},"generative-ai","generative AI",{"_createdAt":6,"_id":71,"_rev":8,"_type":9,"_updatedAt":6,"slug":72,"title":73},"wp-tagcat-documentation",{"current":73},"documentation",{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":6,"slug":75,"title":13},{"current":12},{"_createdAt":6,"_id":77,"_rev":8,"_type":9,"_updatedAt":6,"slug":78,"title":80},"wp-tagcat-software-development",{"current":79},"software-development","software development","Your docs are your infrastructure",{"_id":83,"author":84,"commentCount":89,"comments":30,"excerpt":90,"featureTag":10,"image":91,"publishedAt":94,"slug":95,"sponsored":10,"tags":97,"title":114},"wp-post-20293",[85],{"_id":19,"avatar":86,"name":25,"role":26,"slug":88},{"_type":21,"asset":87},{"_ref":23,"_type":24},{"current":28},5,"We chat with Jared Bhatti and Zachary Sarah Corleissen, two technical writers with deep experience at major tech companies and open source projects, about their approach to documentation and the new book they helped co-author, Doc For Devs. ",{"_type":21,"asset":92},{"_ref":93,"_type":24},"image-472725c034235a56301dc8caf0ed41b3d298c57a-1200x630-png","2022-06-21T04:40:00.000Z",{"current":96},"an-engineers-field-guide-to-great-technical-writing-ep-455",[98,103,105,107,109],{"_createdAt":6,"_id":99,"_rev":8,"_type":9,"_updatedAt":6,"slug":100,"title":102},"wp-tagcat-docs-for-devs",{"current":101},"docs-for-devs","docs for devs",{"_createdAt":6,"_id":71,"_rev":8,"_type":9,"_updatedAt":6,"slug":104,"title":73},{"current":73},{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":6,"slug":106,"title":13},{"current":12},{"_createdAt":6,"_id":50,"_rev":8,"_type":9,"_updatedAt":6,"slug":108,"title":53},{"current":52},{"_createdAt":6,"_id":110,"_rev":8,"_type":9,"_updatedAt":6,"slug":111,"title":113},"wp-tagcat-the-stack-overflow-podcast",{"current":112},"the-stack-overflow-podcast","the stack overflow podcast","Experts from Stripe and Waymo explain how to craft great documentation (Ep. 455)",{"_id":116,"author":117,"commentCount":126,"comments":30,"excerpt":127,"featureTag":10,"image":128,"publishedAt":131,"slug":132,"sponsored":10,"tags":134,"title":144},"wp-post-18282",[118],{"_id":119,"avatar":120,"name":123,"role":10,"slug":124},"wp-author-213",{"_type":21,"asset":121},{"_ref":122,"_type":24},"image-e81c84dcaeb58be1002795a6544b595bd6fc8071-1024x1024-jpg","Ben Popper",{"current":125},"benpopper",1,"Content written by developers, for developers, is a booming business.",{"_type":21,"asset":129},{"_ref":130,"_type":24},"image-6f6591e18674cee2e570564767f3f8ca14c19158-3000x1575-png","2021-06-08T04:40:00.000Z",{"current":133},"podcast-345-a-good-software-tutorial-explains-the-how-a-great-one-explains-the-why",[135,140,142],{"_createdAt":6,"_id":136,"_rev":8,"_type":9,"_updatedAt":6,"slug":137,"title":139},"wp-tagcat-low-code",{"current":138},"low-code","low code",{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":6,"slug":141,"title":13},{"current":12},{"_createdAt":6,"_id":50,"_rev":8,"_type":9,"_updatedAt":6,"slug":143,"title":53},{"current":52},"Podcast 345: A good software tutorial explains the How. A great one explains the Why.",[]]