Posts Tagged: ruby

Discussions / Episodes / Tool Tips — Comments Off
5
Feb 15

Developing CareerOps

It’s been awhile, but we’re finally back, and special guest Katherine Daniels (aka @beerops) is with us to talk over career development in a DevOps context! We discuss All The Things related to leveling up your career, including specialization vs. generalists, training and learning (especially if you don’t have a degree in computer sciency things), and some techniques you can employ to make sure your career doesn’t stagnate! Join us as we delve into:

Developing CareerOps

Join J. Paul Reed, aka @SoberBuildEng,

EJ Ciramella, aka @eciramella, Sascha Bates, aka @sascha_d, J. Michael McGarr, aka @SonOfGarr, and Katherine Daniels, aka @beerops for the discussion, plus the month in News & Views and a brand new Tool Tip!

Or, download Episode 53, or any of our previous shows!

Show Links/Notes

Tool Tip

Paul introduces us to Scott Muc and Subhas Dandapani’s DevOpsBookmarks.com; some hilarity ensues.

(See also: O’Reilly’s similar developer field guide.)


Join Us!

What do you do to make sure your career doesn’t stagnate?

Join the discussion!

Episodes / Panels / Reviews — Comments Off
28
Feb 14

Scaling Your Self-Service as a Service

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:

Scaling Your Self-Service as a Service

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!

Or, download Episode 37, or any of our previous shows!

Show Links/Notes

Review

Paul reviews Venkat Rao’s The Gervais Principle (Or The Office According to “The Office”): losers, clueless, and sociopaths: oh my!

The ebook contains an extra essay on Office Space.

Join Us!

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!

Episodes / Panels / Tool Tips — Comments Off
29
Mar 13

Automate Everything in 48 Hours or Your Pizza Is Free

Imagine waking up to find your site and service hacked. Everyone is running around, trying to find out what went wrong; you’re tasked with repairing the damage. But unfortunately, that automation project you’ve been promising yourself you’d get done has always taken a backburner to more pressing matters and features. With everyone breathing down your neck, wonder where to start. We talk with a panel of engineers who found themselves in exactly this nightmare scenario and follow them as they:

Automate Everything in 48 Hours or Your Pizza Is Free

Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, and Sascha Bates, aka @sascha_d, plus the last couple of weeks in News & Views and a new Tool Tip!

Or, download Episode 17, or any of our previous shows!

Show Links/Notes

Tool Tip

Paul takes a look at NagiosTV, Chris Carey’s tool for displaying Nagios alerts on your metrics/status flatscreens in the office!

Join Us!

What are you own experiences with security incident responses and automation? Where’s the line of infrastructure improvement vs. response? And are there ways to avoid this issue altogether?

Join the discussion!