Speaker

Matthew Oswalt

Matthew Oswalt

Lead Project Engineer

(from https://keepingitclassless.net/bio/)

Matt Oswalt hails from Portland, OR, and focuses on the intersection of network infrastructure, automation, systems, and software engineering. He’s passionate about enabling engineers to evolve their careers to the next level, and sharing the bright spots that exist within the technology industry with the masses.

You can often find him speaking at conferences or meetups about these topics, as well as writing about them on his blog (https://keepingitclassless.net) or on Twitter as @Mierdin.

Automation Curriculum-As-Code with Antidote and NRE Labs

For many infrastructure professionals, the brave new world of automation and DevOps is a bit scary. The problem isn't that they're not capable of learning new things, it's that "automation" can be very ambiguous. There are so many different ways to introduce automation into our systems, and it can be extremely challenging to know where to start.

This "first mile" of learning is something that the open-source Antidote project (and it's reference curriculum, NRE Labs) intends to address. Antidote is designed to make it easy for learners to get started with a variety of automation lessons, by containing a fully interactive infrastructure automation environment entirely in the browser. It also makes it easy for those with something to teach, by representing all curriculum resources as simple text files stored in Git.

By the end of this talk you will:

- Understand more deeply the problem space Antidote intends to address
- Know the technical basics of how the Antidote project works
- Learn how you can get involved with the Antidote project and the open-source NRE Labs curriculum

Network Reliability Engineering - The Network Engineer's On-Ramp to SRE

It's clear that Site Reliability Engineering has taken over the industry. We've gone well past the point where SRE is "that thing Google does", and now we have SRE principles being practiced in all corners of the industry, from the big enterprises to the small startups.

However, the Network Engineering discipline tends to view movements like SRE and DevOps as something that is not intended for them; they view them as something that is limited to the application space. There is a tremendous opportunity for this discipline to learn from the SRE movement, and use the principles that are proven in adjacent industries to make today's networks more reliable, and more responsive to the needs of developers.

A few organizations have begun adopting the title "Network Reliability Engineer" as a way of getting the core SRE tenets and principles into the world of network engineering. In this talk, we'll cover:

- Why network engineers in 2019 have a pretty tough job
- Why NRE exists (and why I think it's useful)
- How the SRE movement can help bring network engineers along for the ride

Matthew Oswalt

Lead Project Engineer

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top