Pinboard (jm)
https://pinboard.in/u:jm/public/
recent bookmarks from jmslides from "Distributed Log-Processing Design Workshop", SRECon Americas 20182018-12-20T11:07:07+00:00
https://www.usenix.org/sites/default/files/conference/protected-files/srecon18americas_slides_virji.pdf
jmdistributed-systems coding design architecture google photon logs log-storage slides sreconhttps://pinboard.in/https://pinboard.in/u:jm/b:c50bc41c6207/The Yelp Production Engineering Documentation Style Guide2018-10-25T10:43:44+00:00
https://engineeringblog.yelp.com/2018/10/yelp-production-engineering-documentation-style-guide.html
jmDocumentation is something that many of us in software and site reliability engineering struggle with – even if we recognize its importance, it can still be a struggle to write it consistently and to write it well. While we in Yelp’s Production Engineering group are no different, over the last few quarters we’ve engaged in a concerted effort to do something about it.
One of the first steps towards changing this process was developing our documentation style guide, something that started out as a Hackathon project late last year. I spoke about it when I was giving my talk on documentation at SRECon EMEA in August, and afterwards, a number of people reached out to ask if they could have a copy.
While what we’re sharing today isn’t our exact style guide – we’ve trimmed out some of the specifics that aren’t really relevant, done a bit of rewording for a more general audience, and added some annotations – it’s essentially the one we’ve been using since the start of this year, with the caveat that it’s a living document and continues to be refined. While this may not be perfect for every team (both at Yelp and elsewhere), it’s helped us raise the bar on our own documentation and provides an example for others to follow.
]]>yelp pe sre ops engineering documentation srecon chastity-blackwell processeshttps://pinboard.in/https://pinboard.in/u:jm/b:6ef5d53a3579/