Our topic for Episode 37 was originally on scaling self-service of configuration management (the source code kind, not the infrastructure kind!) good practices, but quickly morphed into a discussion of what organizations need to pay attention and foster to support their tools teams in their often-cited mission of creating a self-service culture and self-service infrastructure. Paul and Sascha square off over the notions of traditional “service” teams and the newer notion of integrated “tools” (“DevOps?”) teams. We also touch on warning signs for automating self-service processes, including in the CM space, really examining how and why you convert which processes into self-service, ways to get teams to buy into your self-service initiatives, and what’s in the best interests of the entire system that is your software development organization. Join us as we discuss the finer points of:
Join J. Paul Reed, aka @SoberBuildEng, Sascha Bates, aka @sascha_d, Youssuf El-Kalay, aka @buildscientist, and Seth Thomas, aka @cheeseplus for the discussion, plus a the last couple of weeks in News & Views and a review!
- 2:14 – News & Views
- Apple quietly ships an OpenSSL bug fix (but to iOS only?)
- gotos still considered harmful?
- Your car isn’t getting over-the-air updates anytime soon, but possibly not for the reason we’d expect/hope
- Rake creator Jim Weirich passes away; developers pay their final respects on his final Github commit
- WhatsApp purchased by Facebook for $19 billion; Erlang (and FreeBSD) get a bump
- 13:33 – Main Segment: Scaling Self-Service as a Service
- 50:16 – Review
- Paul will be speaking at Mountain West DevOps in Salt Lake City in mid-March!
- USENIX is holding a release engineering-specific conference; CFPs for that are open now
- As always, devopsconferences.com has more conference-deets
Paul reviews Venkat Rao’s The Gervais Principle (Or The Office According to “The Office”): losers, clueless, and sociopaths: oh my!
What issues have you run into while trying to sell or scale self-service initiatives?
Have you had to encode culture into your self-service policies to work around problems?
Join the discussion!