DevOps/SRE Anti-patterns panel discussion

Anti-patterns are solutions to problems that are, usually, ineffective and carry high risks. Although they might appear appropriate and effective, the gains tend to be short-term. Their consequences turn out to be more trouble than they’re worth.

Like many practices, DevOps and SRE have their fair share of anti-patterns and it's tempting to adopt them. Projects might be under budget and time constraints or there might be there a lack of proper skills. When a quick and dirty fix is needed in an emergency, without any malicious intent, there is usually an intention to come back and do it properly, but time and priorities can interfere.

In this panel discussion, our panelists will explore anti-patterns when trying to onboard DevOps/SRE practices into organizations.

About Cláudio Freitas:

Cláudio is a Systems Administrator/DevOps/SRE and all those fancy words that people use to describe guys that work on Systems. He started working in IT from a young age and has been in the game for around 12 years. From Helpdesk to Systems Engineer he has been working as a freelancer in the SRE/DevOps/Systems area.

About Luis Parada:

Luís Parada is Head of Engineering at FARFETCH, currently focused on foundational aspects of the platform such as Observability, CI/CD pipelines, Scalability, and Resilience. Prior to this Parada led Farfetch ID, the group responsible for FARFETCH’s Identity Provider, Authentication & Authorisation, Customer and Partner Account data.

Parada likes to focus a lot on continuous improvement of teams and organizations and on personal development, sharing insights on his YouTube channel and via a Monthly Newsletter called A Leader's Mindset.

About Tiago Ferreira:

From Software Developer, passing through QA Automation Engineer and all the way to Site Reliability Engineer, Tiago has always been focused on promoting software efficiency and reliability by either a direct approach (developing custom software and processes for teams) or by teaching and ramping them up in the DevOps practices. His love for automation (particularly its ability to enable teams to do their best effortlessly) has been the main driver of his career.