Fork me on GitHub
#dockside
<
2020-02-26
>
William Judd16:02:12

Our internal DevOps Book Club meets once a week for half an hour and we discuss two chapters at a time. The pace seems to enable a kind of "side" engagement that would otherwise be lost amid all the critical priorities of daily work. This week we're up to chapter 15 of The Unicorn Project.

👏 1
William Judd16:02:12

Our internal DevOps Book Club meets once a week for half an hour and we discuss two chapters at a time. The pace seems to enable a kind of "side" engagement that would otherwise be lost amid all the critical priorities of daily work. This week we're up to chapter 15 of The Unicorn Project.

👏 1
James Heimbuck16:02:22

my TUP book club at work took about 2 weeks between meetings and did a full section at a time. it was a lot to remember and talk through. the approach you are taking sounds more manageable.

👍 1
William Judd16:02:38

We've read 20 books in 4+ years so I guess we average about 6 weeks per book.

👍 1
Ben Wiechman13:02:02

Can you describe the format of the meetings? How many participants? How do you structure them? Has someone typically read the book first and then suggests it to the rest of the team? We just created our first SRE position, and this was the tactic we had considered to work through the SRE role and identify the cultural and process changes that would be required to achieve the desired end results.

William Judd05:03:00

Hi, Ben. I guess the format is a type of open seminar but everyone is on equal footing as we usually select a book no one has read. Meetings range between six and twelve participants. People volunteer to write up chapter summaries which we publish centrally along with our key take-aways, passages we liked, links to other references, etc.