SF Reliability Engineering - August Talks

Doors at 6pm and ID required in the lobby. We're starting the talks at 6:30pm. Food and drinks provided.

--

We're always looking for 20-30 minute technical talks (and 5-8 minute lightning talks) relating to the very broad field of Reliability Engineering. Get in touch with the organizers if you'd like to present!

Important check-in details for Twitter:

1. Bring your photo ID. This is required by building security during the check-in process.

2. We will begin checking people in at 6:00pm. Check-in closes at 6:30pm, so please arrive on time!

(If you arrive after 6:30pm, you may message the organizers on Meetup.com and we will do our best to get you into the event. However, please note that we are unable to check-in any attendees after 6:45pm)

--

Twitter Developer Community Code of Conduct:

Events hosted at Twitter are covered under the Code of Conduct: https://developer.twitter.com/en/community/code-of-conduct.html

--

Talk #1: Reliable event collection without an ops army

Description: After years of running on self-managed hardware, Quantcast’s system for collecting our most critical events from the edge was poorly suited for a migration to an ephemeral, public cloud. By focusing on simplicity and identifying clean points of integration, we were able to perform a fully transparent migration to a new service with better performance and reliability. We’ll share some of the technologies involved in making this possible, and the lessons we learned along the way.

Bio: Noah Goldman is a Software Engineer at Quantcast, working on internal tooling around Kubernetes as well as Quantcast’s underlying platform for collecting web analytics data. He has previously spent time working on an internal job scheduling tool, as well as improvements to metrics collection systems. He enjoys playing Volleyball competitively whenever possible in his free time.

--

Talk #2: Changing The Game: Leveraging Game Theory to Transform Your IT Organization

Description: As organizations begin the process of digitally transforming they will often struggle after initial efforts at automation (the dreaded J-curve). In this 30 minute session we'll discuss why the J-curve phenomenon occurs and define the concept behind the Pareto Inefficient Nash Equilibrium through a game show called "Golden Balls". In this entertaining segment we'll discuss how you can introduce this concept to effectively change the game and push past the low-end of the J-curve.

The journey doesn’t end there, as organizations begin shipping changes more often, introducing new features, services, and dependencies complexity begins to rise. We’ll also discuss how SRE teams can leverage distributed tracing aggregates, system metrics, and log analytics to effectively measure “all the things” and the value this measurement brings to engineering teams through visibility, communication, and accountability.

Bio: Kevin Crawley works for Instana, a managed service provider that specializes in observability and monitoring production systems, as a Developer Advocate. A Docker Captain, Kevin has traveled the globe speaking on topics including DevOps, Docker, Observability, and Culture Transformation. At his previous jobs Kevin was responsible for designing and building distributed scheduling systems utilizing Amazon SQS, DynamoDB, Kinesis and Redshift. In his most recent project, he was responsible for a modern software delivery platform using Go/Angular which was integrated with Docker Swarm and Gitlab.