How to Hire and SRE in 5 minutes - Max Timchenko - DevOpsDays Tel Aviv 2017

•

0 likes•429 views

DevOpsDays Tel Aviv

DevOpsDays Tel Aviv 2017

Technology

How to hire a SRE
in 5 minutes
MAX TIMCHENKO
SRE II
TLV 
2017

@maxvtDevOps Days TLV 2017
“SRE”?
2
“We enable service owners to focus
on rapid delivery of value to
PagerDuty customers by providing
common infrastructure, self-service
tooling, best practices, and subject
matter expertise.”

@maxvtDevOps Days TLV 2017
Not “SRE” (at PagerDuty)
3
• Operating all the things
• Being a language/framework expert
• Gate-keeping access to production
• Forcing specific processes on teams

@maxvtDevOps Days TLV 2017
HumanOps
4
“Words are important
and very hard.”
@arupchak
Infrastructure Director, PagerDuty

@maxvtDevOps Days TLV 2017
HumanOps Skills
5
• Not an ***hole
• Can listen
• Can mentor and explain
• Writes good documentation
• Gets stuff done
• Understands on-call
• Eats food

@maxvtDevOps Days TLV 2017
Technical Skills
6
• Networking (the computer kind)
• Release engineering, CI/CD
• Software engineering
• Application stacks, platforms
• Configuration management
• Monitoring, observability, alerting
• Linux operations and performance
• Security

@maxvtDevOps Days TLV 2017
Application Stacks / Platforms
7
• Load balancing
• Service discovery
• Distributed systems
• High availability
• Secret management
• Cluster managers
• Platform-as-a-service

@maxvtDevOps Days TLV 2017
Evolution of Tech Skills and Scale
8

@maxvtDevOps Days TLV 2017
Team Composition
9
Product Owner
Manager
1x SRE III
3x SRE II
2x SRE I
Scrum Master

@maxvtDevOps Days TLV 2017
Rank Missing Skills
10
Need Borrow? Skill
⭐⭐⭐ No Continuous Deployment
⭐⭐ Yes Managing Complexity
⭐⭐ Yes Software Engineering
⭐ No Config Management
“Borrow”: can we borrow this skill  
from elsewhere in the company?

@maxvtDevOps Days TLV 2017
Job Description
11

@maxvtDevOps Days TLV 2017
“It is so difﬁcult to hire”
12
• Do you need “10 years of AWS
Lambda experience”?
• Similar skills, not exact match
• Embrace non-traditional backgrounds
• Offer remote and flex time

@maxvtDevOps Days TLV 2017
SRE Backgrounds
13
© Disney/Pixar; https://herure.deviantart.com/art/Monsters-Inc-autographs-151458694

@maxvtDevOps Days TLV 2017
Interview Process
14
• Phone screen, with coding question
• On site interview, up to a full day
• Up to 6-8 different interview slots
• Technical, project, and people skills

@maxvtDevOps Days TLV 2017
Interview Slot Examples
15
• System design
• Frontend frameworks
• Business acumen
• Everyday coding

@maxvtDevOps Days TLV 2017
Discussion Questions
16
“What would you do if you suspect replicants
gained access to your production infrastructure?”

@maxvtDevOps Days TLV 2017
Hands-On Questions
17
© 1999 Warner Bros. Entertainment Inc.

@maxvtDevOps Days TLV 2017
Disposable Interview Environments
18

@maxvtDevOps Days TLV 2017
Evaluation and Scoring
19
‫המנחם‬ ‫יוני‬ :‫יח''צ‬ ‫כוכבים צילום‬ ‫עם‬ ‫רוקדים‬ ‫של‬ ‫הראשונה‬ ‫בעונה‬ ‫לוי‬

@maxvtDevOps Days TLV 2017
20
Would You Like To Know More?
Jason Grimes, “Archetype of a SRE Superhero”, DoD PDX ‘17 
https://www.youtube.com/watch?v=BPmr7F5dXWc
Camille Fournier, “Building & Motivating Eng Teams”, OSS Leadership Summit ’17 
https://www.youtube.com/watch?v=7R-Y2DwWOr0
@maxvt
https://www.pagerduty.com/careers
Hearing about our SRE team makes you want to be a part of it?

Similar to How to Hire and SRE in 5 minutes - Max Timchenko - DevOpsDays Tel Aviv 2017

Integration-Monday-Logic-Apps-Tips-Tricks

BizTalk360

10 tips you should know for being more productive and building more reliable, effective Logic Apps. In this session, we will do a reflection to your existing Logic Apps processes and when thru a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective workflows. At the same time, these will allow you to be more productive and document your workflows from the beginning.

ACSUG June 2020 - Azure Logic Apps: Best practices, tips and tricks

Sandro Pereira

The Briefing Room with Dr. Robin Bloor and RedPoint Global Live Webcast on September 23, 2014 Watch the archive: https://bloorgroup.webex.com/bloorgroup/lsr.php?RCID=6cd94ed2ed7cc7090f7d5db1bf343438 Ask anyone who knows, and they’ll tell you candidly: traditional Master Data Management programs require not just tools, technologies and people, but also a level of cooperation and collaboration in the business that can be very difficult to manage. Many of the consequent hurdles that appear stem from long cycle times and lack of transparency into the creation and management of the rules that govern such programs. But now, the power of Hadoop 2.0 has opened up a very different method of action. Register for this episode of The Briefing Room to learn from veteran Analyst Dr. Robin Bloor who will explain how the Hadoop ecosystem, powered by YARN, can transform MDM from a segmented, often disjointed set of business processes, into a much tighter platform that can finally deliver on the original promise of the discipline. He’ll be briefed by George Corugedo of RedPoint Global, who will showcase his company’s unified data management platform, which weaves together the best practices of traditional MDM with the power and flexibility of Hadoop. Visit InsideAnlaysis.com for more information.

Has Traditional MDM Finally Met its Match?

Inside Analysis

MapR and Machine Learning Primer

Mathieu Dumoulin

Much of the adoption of Agile and DevOps tools and processes focus on the benefits to delivering high quality code on an industrial scale. Although we all recognise that good visual representations of progress and status are critical, it may not be obvious that the act of visualisation can have a profound effect on the attitudes and culture of the teams involved. The right sort of data and appropriate dash-boarding can improve the morale and effectiveness of all the teams involved. The wrong sort of can have the opposite effect. This talk examines how what you share will define you. Through real examples and a live demo, the speaker will show you how to design status and trend displays that will make your teams more effective without overloading them. The talk will also include case studies with various types of teams to highlight how you can apply this thinking to help make any group more effective.

Agile Tour London 2018: DASHBOARDS AND CULTURE – HOW OPENNESS CHANGES YOUR BE...

Steve Poole

Abstract: DevOps has been one of the game changers to accelerate Collaboration and Automation to drive Speed to Market (Development priorities) and Availability/ Stability/ Performance etc. (IT Operations priorities) for last 8+ yrs. Fast forwarding, Gartner’s 2018 Hype Cycle for Performance Analysis named DevOps and AIOps as two areas that have gained the most momentum in the industry .In essence , AIOPS has helped in shaping DevOp smarter and intelligent i.e. DevOps Systems that Do -> Think -> Learn. Engineering maturity of FAANG (Facebook, Amazon, Apple, Netflix, Google) companies are already in the journey of NoOps - the point where an IT environment becomes so automated that a dedicated team isn’t even needed for managing tasks anymore. For engineering teams to nurture the belief that “machines should solve known problems and engineers must focus on solving new problems,” which essentially means saying NO to manual IT operations. Key Takeaways: 1. Everything As Code 2. Platform as Service 3. DevOps maturity beyond automation 4. Site Reliability Engineering (SRE) 5. Software Engineering Culture.

Agile Gurugram Conference 2020 | Value of DevOps - Journey from Automation to...

AgileNetwork

Cloudy with a Chance of Databases

Kellyn Pot'Vin-Gorman

Kieron Sambrook-Smith, Chief Commercial Officer at Platform.sh spoke at eZ Conference 2017 in London about the business value of Platform as a Service (PaaS) Automation. He covers the many aspects of the advantages of using a PaaS. The business value you can expect to reap will range from hosting cost savings, better workflow and team productivity, new project delivery concepts, and greater competitive advantage. Discover a more advanced implementation of your service offering.

The Business Value of PaaS Automation - Kieron Sambrook-Smith - Presentation ...

eZ Systems

RightScale User Conference: Why RightScale?

Erik Osterman

New DevOps for the DBA

Kellyn Pot'Vin-Gorman

Dev ops lessons learned - Michael Collins

Devopsdays

From Microservices to Service Mesh - devcafe event - July 2018

Thang Chung

A New Hiring Paradigm

MaRS Discovery District

Speakers: Uri Budnik - Cloud Evangelist, RightScale Arindam Mukherjee - Sr. Manager DevOps, Blackhawk Network IT organizations are turning processes and practices often referred to as DevOps in order to speed up application delivery, shorten release cycles, improve quality, and better meet the needs of their business. We will present a real-life story of an organization implementing DevOps and leave you with best practices for use in your own organization.

DevOps Stories: Getting to Agile - RightScale Compute 2013

RightScale

HRMS Online Software

Tech2Globe Web solutions LLP

resume

Brent Ransom

While service meshes may be the next "big thing" in microservices, the concept isn't new. Classical SOA attempted to implement similar technology for abstracting and managing all aspects of service-to-service communication, and this was often realized as the much-maligned Enterprise Service Bus (ESB). Several years ago similar technology emerged from the microservice innovators, including Airbnb (SmartStack for service discovery), Netflix (Prana integration sidecars), and Twitter (Finagle for extensible RPC), and these technologies have now converged into the service meshes we are currently seeing being deployed. In this talk, Daniel Bryant will share with you what service meshes are, why they're well-suited for microservice deployments, and how best to use a service mesh when you're deploying microservices. This presentation begins with a brief history of the development of service meshes, and the motivations of the unicorn organisations that developed them. From there, you'll learn about some of the currently available implementations that are targeting microservice deployments, such as Istio/Envoy, Linkerd, and NGINX Plus. Attendees will walk away from the talk with a high-level overview of the concept, tools for deciding when best to use a service mesh, and a getting started guide if they decide this technology is the right fit for their organisation.

CloudNativeLondon 2017: "What is a Service Mesh, and Do I Need One when Devel...

Daniel Bryant

Converged and Containerized Distributed Deep Learning With TensorFlow and Kub...

Mathieu Dumoulin

Rails is optimised for the first weeks of development. At the later phases it's no longer the speed of adding new views and data that matters. It's often more about the different (and changing!) ways of using the data. The business logic gets more complicated. DDD has answers to those problems. Detecting the bounded contexts is the crucial skill. Choose which parts of the app leave as CRUD and which could go into more of the tactical DDD.

From Rails legacy to DDD - Pivorak, Lviv

Andrzej Krzywda

A field guide to the Financial Times, Rhys Evans, Financial Times

Neo4j

Similar to How to Hire and SRE in 5 minutes - Max Timchenko - DevOpsDays Tel Aviv 2017 (20)

Integration-Monday-Logic-Apps-Tips-Tricks

ACSUG June 2020 - Azure Logic Apps: Best practices, tips and tricks

Has Traditional MDM Finally Met its Match?

MapR and Machine Learning Primer

Agile Tour London 2018: DASHBOARDS AND CULTURE – HOW OPENNESS CHANGES YOUR BE...

Agile Gurugram Conference 2020 | Value of DevOps - Journey from Automation to...

Cloudy with a Chance of Databases

The Business Value of PaaS Automation - Kieron Sambrook-Smith - Presentation ...

RightScale User Conference: Why RightScale?

New DevOps for the DBA

Dev ops lessons learned - Michael Collins

From Microservices to Service Mesh - devcafe event - July 2018

A New Hiring Paradigm

DevOps Stories: Getting to Agile - RightScale Compute 2013

HRMS Online Software

resume

CloudNativeLondon 2017: "What is a Service Mesh, and Do I Need One when Devel...

Converged and Containerized Distributed Deep Learning With TensorFlow and Kub...

From Rails legacy to DDD - Pivorak, Lviv

A field guide to the Financial Times, Rhys Evans, Financial Times

More from DevOpsDays Tel Aviv

From idea to execution, the challenges of publishing an open source project are very similar to initializing a startup when it comes to creating a successful product that people will love and use. Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project. In this talk, I will use my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...

DevOpsDays Tel Aviv

If you have never used GraphQL before, you probably think that it is just another buzzword that will be forgotten in a few years. You might think: “Why do I need to learn a new way to write APIs when REST already answers all my needs?”. Or, you are excited to learn something new but don’t believe GraphQL is mature enough for production. In this talk, I will remind you of some of the pain points you have probably experienced when using REST. I will then explain what GraphQL is and demonstrate how it solves these pain points. Next, I will discuss the disadvantages of GraphQL. Finally, I will provide some guidelines for choosing between REST and GraphQL. By the end of this talk, you will understand what GraphQL is and when to use it.

GRAPHQL TO THE RES(T)CUE, ELLA SHARAKANSKI, Salto

DevOpsDays Tel Aviv

“The International Space Station has been orbiting the Earth for over 20 years. It was not launched fully formed, as a monolith in space. Instead, it is built out of dozens of individual modules, each with a dedicated role - life support, engineering, science, commercial applications and more. Each module (or container) functions as a microservice, adding additional capabilities to the whole. Not only do the modules need to function together, delivering both functional and non-functional capabilities, they were designed, developed and built by different countries on Earth and once launched into space (deployed in multiple different ways), had to work together - perfectly. Despite the many (minor) reliability issues which have occurred over the decades, the ISS remains a highly reliable platform for cutting edge scientific and engineering research. In this session I will describe the way the space station was developed and the lessons Site Reliability and DevOps Engineers can learn from it.

MICROSERVICES ABOVE THE CLOUD - DESIGNING THE INTERNATIONAL SPACE STATION FOR...

DevOpsDays Tel Aviv

Have you ever felt you took every wrong turn possible in the process of mitigating a production incident? Did you go through a 3-hour hell during incident response and felt the incident wasn’t complex enough to justify the horrors you’ve experienced? Did it cause you to question your engineering or problem-solving skills? Well, it’s only partially you. Our brain is wired to make decision-making simpler. In doing so, it exposes itself to biases, heuristics, and other quirks that may seem like “bad decisions” in hindsight. In this talk, through real-life outages, we’ll project those psychological principles onto the world of production monitor, and incident management. As a responder, you’ll learn why those behavioral patterns emerge during production incidents and what can be done to limit their effect, and as a manager, you’ll learn how to enable and encourage a healthy environment to better support those patterns.

THE (IR)RATIONAL INCIDENT RESPONSE: HOW PSYCHOLOGICAL BIASES AFFECT INCIDENT ...

DevOpsDays Tel Aviv

The word observable entered the English language roughly 400 years ago, but the concepts of what it means to see, comprehend, and understand something have been debated since time immemorial. Starting in the 19th century, a series of postulates and criteria coalesced into control theory, and it is from this body of knowledge that we gained the word “observability”. Today, with the advent of complex, interconnected computer systems, that word has taken on new meanings and connotations—some useful, some detrimental, and some just plain confusing. In this talk, we’ll mix a little history, a touch of philosophy, and a healthy dose of reality, to demystify what observability means to us as professional computer people. We’ll tear through the marketing material and unearth foundational principles that will help us to build better infrastructure, write better software, and promote healthier business practices. Finally, we’ll explore some potential new avenues for discussion and understanding.

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDog

DevOpsDays Tel Aviv

Security people say users are the weakest link. But are they? When complying with security becomes too burdensome, users take shortcuts, find workarounds, and end up jeopardizing security. Blaming users is lazy and easy. Making security usable is time consuming and challenging. How does design research help us understand our customers? What patterns and principles drive secure behavior? How can we build empathy with customers and make the right thing to do the easiest thing to do? This session explores these questions, and provides examples of how design thinking and research can help us be more secure. We will walk through our creation of core user personas, design principles, and how these inform and direct our design choices and intent. Don’t blame your users anymore. Come learn how to be part of a future where usability leads security.

NUDGE AND SLUDGE: DRIVING SECURITY WITH DESIGN // J. WOLFGANG GOERLICH, Duo S...

DevOpsDays Tel Aviv

This is for you, you rockstar, ninja coffee drinking workaholic who doesn’t know what a vacation day looks like. Even though you love your job and are dedicated and are super important, you need a break too. We tend to think that working all the time is an effective practice while the truth is that finding the time for self care and recharging your batteries is beneficial for both you and your company. Additionally, if you’re a leader, you’re responsible for the wellbeing of your team. In this talk I’ll discuss the importance of taking time off of work and creating a positive culture surrounding vacation time.

(Ignite) TAKE A HIKE: PREVENTING BATTERY CORROSION - LEAH VOGEL, CHEGG

DevOpsDays Tel Aviv

This is a story about taking the cloud infrastructure of a successful company, that is still managed as infrastructure of a startup company, and rebuilding it to support the growing business requirements, especially around disaster recovery and business continuity. In the session I will share Next Insurance’s journey - where we started, where we are now and what we learned on the way so far. I will talk about how we managed to build our proven DR plans, and actually execute them in our DR drills. I will also talk about why we decided that the only way to prove your DR plan works is to continue running your business in the DR account and make it your production account, and go on to build your next DR account. If you are a part of a company that is about to embark on a similar journey, this session might equip you with some very useful insights on how to think about such a challenge, and some very useful and practical tips on how to execute it.

BUILDING A DR PLAN FOR YOUR CLOUD INFRASTRUCTURE FROM THE GROUND UP, MOSHE BE...

DevOpsDays Tel Aviv

CI/CD pipelines are quickly becoming the path of least resistance for would-be attackers into sensitive internal systems, gaining access to critical data, with minimal effort. In the InfoSec world when we talk about CI/CD security often times this focuses on specific aspects of securing your pipeline - scanning the code, protecting secrets, securely managing code deployments, or even authentication and authorization mechanisms, but we rarely talk about all of these together. After years of being in the trenches and realizing that the attack surface is growing and the threat landscape becoming more and more complex, it has become increasingly apparent that security teams need to adapt and modify strategies to keep up with the new reality of CI/CD protection, without compromising developer velocity. In this talk I would like to propose a new way of thinking about CI/CD security - that encompasses the three disciplines that comprise CI/CD security - security in the pipeline, of the pipeline, and around the pipeline. Partial coverage of any or all of these disciplines simply will not cut it with the continuously evolving risk landscape. Security engineers need to address each of these aspects in their entirety to provide the full scope of coverage that modern organizations need, and I will take a deep dive on the challenges each introduce, and the approaches and techniques for mitigating them based on adversarial sec research.

THE THREE DISCIPLINES OF CI/CD SECURITY, DANIEL KRIVELEVICH, Cider Security

DevOpsDays Tel Aviv

Configuration Management is at the core of Ops. It’s the biggest enabler of any compute operation, small and big. In the past decade, we have switched from thinking about the machines we are configuring, to think about the software and services we are controlling. With that change of mindset, so did the tools we are using. Traditional tools like Puppet, chef, salt and Ansible are slowly declining while new tools such as Terraform, Pulumi, Helm and Kustomize are on the rise. In this talk I will try to describe the pain-points and the opportunities of this transformation as well as suggesting a future direction based on tools developed at the big-tech companies (Mainly facebook and google).

CONFIGURATION MANAGEMENT IN THE CLOUD NATIVE ERA, SHAHAR MINTZ, EggPack

DevOpsDays Tel Aviv

We all know how hard it is to find DevOps engineers, and creating a diverse team despite gender and ethnicity bias? Nearly impossible. At this talk we will show our tools and methods implemented in the Develeap hiring process that overcome this inherited bias. About 2 years ago we faced a crisis in our DevOps consulting company - the market demand was higher than we could supply. The traditional recruiting process depending on CV and artificial credentials was not working. So we came up with an alternative solution, and since then - we are growing exponentially and diversely. In this talk we will show the practical tools we deployed in order to increase our capacity, and we will show how these tools overcome the inherited bias in the process.

SOLVING THE DEVOPS CRISIS, ONE PERSON AT A TIME, CHRISTINA BABITSKI, Develeap

DevOpsDays Tel Aviv

Everyone wants observability into their system, but find themselves with too many vendors and tools, each with its own API, SDK, agent and collectors. With the increasing complexity of modern applications, continuous profiling methods and tools are gaining popularity among the Developer and Engineering communities. In this session, we cover what continuous profiling entails and why you should implement a profiler into your tech stack (if you haven’t done so already). We’ll then bring theory to practice and demonstrate a real-life scenario using gProfiler, a free open-source continuous profiling tool, covering Linux servers on multiple architectures (such as Graviton).

OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...

DevOpsDays Tel Aviv

“Being oncall sucks. But it doesn’t have to!” We all heard this one before. Why is it though, that oncall still remains the biggest scar for many? What can a modern Engineering org do to rein the oncall dragons, and actually help people grow as professionals as they go oncall? In this talk, I will present the main reasons why oncall is difficult in modern orgs, and describe ways to mitigate these hardships. The idea is that oncall is often the ‘backroom’ of an org, where all the technical and organizational debt take their toll. Be it unwieldy systems or broken processes between teams, oncall checks all the ‘weak boxes’. Therefore, the only way to win at oncall is to sort out your debts, starting with the organizational ones. I will dive into the detail of the oncall rotation at Snyk as the org scaled from 1 to 220 people, what worked well about it, and what was less than perfect. I will discuss the decisions made to turn oncall into a building block of the org, and show a path to rein oncall in your organization as well.

HOW TO SCALE YOUR ONCALL OPERATION, AND SURVIVE TO TELL, ANTON DRUKH

DevOpsDays Tel Aviv

Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks. This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example: Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira. You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have. You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.

HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB

DevOpsDays Tel Aviv

Do you know what it feels like to navigate as someone who can’t distinguish between green and red - looking at those badges that tell you whether something is broken or a-okay? I’ll give you a quick look into what it feels like with some examples from the monitoring tool Icinga Web 2. We all tend to forget, that not everyone sees the world like we do. In this talk I’ll be walking you through different views in Icinga Web 2 with side-by-side comparisons for the default views and how different kinds of vision impairments affect those. The talks also features a few suggestions on how to improve colour schemes and making websites and webapps better to navigate with screen readers!

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

DevOpsDays Tel Aviv

Recent years have exposed startups to a major plague - cloud overspend. No vaccine appears to exist, plethora of tools and consultants fail to stop the bleeding. And yet, some companies manage to stay safe. What makes them different? Is it the tools? Is it the mindset? Is it developer training? In this session we will examine the cultural factors involved in sound and responsible financial management in the cloud. We will also look at relevant system design elements and product design elements which enable us to spend wisely while our business runs smoothly. Following this session, you should be better versed in cost-aware system design and some of the cultural and structural requirements to keeping your cloud bill low.

(Ignite) WHAT'S BURNING THROUGH YOUR CLOUD BILL - GIL BAHAT, CIDER SECURITY

DevOpsDays Tel Aviv

In every development process there is the question, do we invest enough on quality? Do we need to invest more? Every team knows about the dilemma of how many tests is the right amount of tests we should write. Is 80% test coverage is good enough? Maybe 90%? 100%? Should we invest more time in unit testing? Are we wasting too much time on unit-testing? Should we invest time on a faster rollback mechanism? WIIFM “Without data, you’re just another person with an opinion” - W. Edwards Deming SLO Driven Development is a framework that helps the developers focus on impact and balance of every aspect of the dev process. When working currently with SLI, SLA, SLO and error budget you can learn where to invest in the development process. Let’s talk about the importance of good SLOs and how they can help us improve our day2day

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.io

DevOpsDays Tel Aviv

In this talk, I will share do's and don'ts on how to onboard successfully in a remote or hybrid setup including moving to a leadership role, speaking from my own journey onboarding remotely in the midst of a global pandemic. I will share the tips that worked for me for successful onboarding, how I was able to be productive, impactful, and make a good impression on others. The key issues as an “onbordee” that I will talk about are how to create relationships, make yourself visible in the company, time management, and more. Since I started working in Augury over 100 new employees have joined the company. Each month I give a session that is part of their general onboarding process. This became a crucial step due to the fact that we are now a hybrid company and a lot of people are onboarding remotely or in a hybrid setup for the first time in their lives. I joined the company as a backend developer and a few months into my role, the squad leader position in my squad was up for grabs and I was fortunate enough to grab it :) This is my first official leadership role, which I also needed to onboard into in a hybrid setup. I will share the process that I built for myself on “How to lead”. Also, a word or two on the process we built as a squad on how we work in a hybrid setup, what are we optimizing for when we do meet and how to include new members of the team.

ONBOARDING IN LOCKDOWN, HILA FOX, Augury

DevOpsDays Tel Aviv

In your ever-changing Infrastructure, some changes are intentional while others are not. Drift is what happens whenever the real-world state of your infrastructure differs from the state defined in your configuration. This can happen for many reasons, sometimes it happens when adding or removing resources, other times when changing resource definitions upon resource termination or failure, and even when changes have been made manually or via other automation tools. While Terraform itself can detect drifts, in most cases, you will be informed about it too late: just before you are about to deploy new changes to your infrastructure. What’s interesting about Terraform though, is that you can apply changes in two separate and distinct steps of “Planning” and “Applying”. This means that you have full visibility of what Terraform is planning on doing beforehand, and if you are satisfied with the changes, you can choose to apply them. So how does this work? When something is changed intentionally, it will appear in the source code, and the Terraform plan will not do anything. However, if any part of the infrastructure has been changed manually, Terraform’s plan will identify this, and alert you to the change. In other words, if your IaC drifted from its expected state, then Terraform’s plan will, in fact, detect it. Applying this simple solution can empower DevOps and developer velocity, with the reassurance and context for unexpected changes in your IaC, in near real-time. This talk will showcase real-world examples, and practical ways to apply this in your production environments while doing so safely and at the pace of your engineering cycles.

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly

DevOpsDays Tel Aviv

KEYNOTE | WHAT'S COMING IN THE NEXT 10 YEARS OF DEVOPS? // ELLEN CHISA, bolds...

DevOpsDays Tel Aviv

More from DevOpsDays Tel Aviv (20)