Agenda

Like our New Horizons village, our community of applications interacts with each other, not just us. What kind of rules of polite society can we set for them so that we can all get along without fighting, and adapt well when someone moves out? When we talk about microservices, the implication is that it’s something that we’ve built, but many of the same interaction rules can (and should?) be applied to our external tools.

This talk is for people who are working in an environment where the only constant is that tools will change and resources won’t.

One of the major trends in contemporary cloud-native application development is the adoption of GitOps; managing the state of your Kubernetes cluster(s) in Git - with all the bells and whistles provided by modern Git platforms like GitHub and GitLab in the regards to workflows, auditing, security, tooling, etc.

Let’s dive in into how your teams can leverage it for a faster and safer road to production!

What does software engineering and Animal Crossing have in common? Building happens in real time, so you need to be strategic in how you allocate your time. Should I be planting apple trees, or selling turnips? Should I be cost-optimizing these databases, or replacing that legacy infrastructure? This talk will present some strategies to set your engineering team up for success in a world where your time is as valuable as a gold nugget.

We all know how easy it is to deploy our app / infra / container / service, but is it easy is it to make sure they’re monitored and secure? We’re always the ones responsible for replying to that strange email to security@ or waking up to some unusual issue so why not understand some fundamentals to get better at responding.

Jake discusses some security fundamentals that will make that next security incident a little less painful using open source tools, and tactics available to anyone - and will cover the things to do when you’re feeling the security incident ‎️‍🔥‎️‍🔥‎️‍🔥,

When we all went to our individual islands, the experience didn’t look the same for everyone. Some had others on their islands while others only had their landlord and other villagers for company. Some of us lived on our islands long before others were forced to theirs. As we began to reconnect and our time on our islands lasted longer and longer, we had to review exactly how we would communicate. We could “visit”, but it required coordination. We could send letters, but that took time. One thing we all needed to learn was how to work together, no matter which island we were on.

This talk will address:

• Different Asynchronous and Synchronous Channels
• How to Maximize Synchronous Communication
• Asynchronous Etiquette
• The Remote Watercooler

This talk sets ground rules and expectations for fully distributed communication and collaboration. These general rules are good for any distributed team member to keep in mind.

Writing code is something that we learned. Managing a project E2E - Probably not that much.

In this talk, I’ll share my journey of migrating the entire R&D’s codebase from BitBucket to GitLab on my own - But with the great help of people along the way - Planning, implementation, and handoffs.

I’ll share best practices for managing a technical project with a lot of takeaways you could adopt so your project will be handled smoothly and successfully.

In the corporate world, a strategic plan is used by organizations to define their vision, goals and objectives. So why don’t we use this amazing tool in our personal life? Creating your personal strategic plan can help you stablish a direction, identify your goals and design the life you want to have.

Have a task that’s supposed to be easy? You could do it in a snap? You know you really should get it done, and yet… you just can’t bring yourself to do it?

This talk presents the concept of the Wall of Awful, a metaphor for emotional barriers that keep us from doing the things we supposedly want to do, the neuroscience behind these blockers, and tactics for getting past them and to your goal.

From managing custom-built bespoke servers in data centers, to spinning up serverless applications in the cloud, monitoring and observability has undergone a generational shift over the past decade.

Today, most companies implement expansive monitoring of their production applications to quickly respond to customer issues as they arise. The trouble is, by the time customers experience a problem or security issues are found, it’s already too late. In this session, we’ll talk about:

• Four rising industry software development trends.
• Why software design and code quality are the next challenges for building resilient software.
• How the current generation of observability tooling is failing modern enterprises
• How to move observability directly into the developer’s coding workflow to surface performance, reliability and security issues before code is ever committed

It’s widely accepted that DevOps is as much a cultural shift as it is about the technology that’s used. DevOps consists of four main pillars, one of which is collaboration.

In this session I’ll talk about why collaboration is important and how developers and non-developers can work better together. I’ll also gives you some tips on tools to use for more effective collaboration and teamwork across multidisciplinary teams.

In this panel, a group of alumni speakers, organizers, and friends of the show will discuss the history of Deserted Island DevOps, and how it has evolved over the past few years.

Note: This panel is exclusive to VIP ticket holders.

Every company on the planet either has, or wants to have, a community. For many this is a marketing tool – a source of free content generation, or word of mouth promotion, or simply repeat customers. In open source, the community plays a much more key role. The community is responsible not just for the aforementioned things, but also for the maintenance of the product and the happiness of end-users.

Without a healthy, active, and growing group of people donating their time, skills, and emotional energy to free of charge, the product might not exist. Ensuring that community flourishes means investing in fostering trust on both sides, and allowing a certain degree of autonomy. This can become very complicated to manage, though; people are messy, and perspectives will differ between the community and the business. How do we succeed here? How do we balance the will of the community and the needs of the business? And when differing perspectives clash (because they will), how do we manage the loss of trust and come out stronger for it?

This talk will discuss how to package ML models to facilitate inference, interoperability, and monitor pipelines to systematically build, deploy, and govern ML solutions for businesses and industries. Additionally, we will comprehend numerous insights into MLOps coupled with real-world examples in Azure to write programs that train robust and scalable ML models which are deployed securely in production.

Team knowledge, configurations, and infrastructure access can be challenging in a distributed world. Have you ever asked “what’s that command we use?” or “Where are the secrets to access that environment?” - well this talk is for you!

We’ll explore using Oh-My-Zsh, a powerful Zsh configuration framework, in order to share team knowledge, distribute common configurations, and share infrastructure access. We’ll discuss the real world scenario this use case emerged from, challenges faced in this approach, and how you can leverage Oh-My-Zsh for your distributed devops teams.

Cloud-native technologies and methodologies such as Kubernetes, infrastructure as code (IaC), and GitOps have drastically changed the way we build applications. The way we secure those applications needs to evolve as well.

We’ll start with a pre-built, insecure deployment pipeline and work backwards to learn common Kubernetes security misconfigurations and how to prevent them through automated guardrails. The environment will be available to all attendees to follow along or deepdive for themselves after the session.

Fatima and Daniel, BFFs IRL and island neighbors, talk about their journey into DevOps starting from 0. Let’s face it, DevOps is intimidating - there are so many moving pieces that are constantly changing. It can be overwhelming to understand the technical concepts, interact with niche communities, and start building with all the cool new tech, especially if you’re new, much like building an island from scratch 🌴.

As newcomers to the DevOps community, Fatima and Daniel will share strategies for survival, the resources they used, and what they learned on the way. There’s an art to asking questions, connecting with the community, learning in public, and most importantly, building projects with Kubernetes. Yes, there is a wrong way to build with Kubernetes 🙃.

Join us for a wonderful, flower planting, fruit picking, and fossil collecting journey of professional growth and friendship, powered by DevOps & Turnips.

Observability helps engineers understand the systems they have built, but it can also help engineers new to your team and even engineers new to tech understand the systems they will be working on.

In this talk, we will explore what it means to build a culture of observability within engineering teams, how a culture of observability fosters a culture of learning, and how these practices build a foundation to do things like onboard new engineers more effectively, help engineers level up, and take on apprentices.

A lot has happened in the past 10 years (give or take) of DevOps. What started as a single tech conference in Belgium became 80 worldwide events in 2019 and persists throughout a global pandemic as online gatherings. And while the tech du jour of these events has shifted over time —conferences full of talks and open spaces on jenkins pipelines give way to docker and now to kubernetes talk— we’re still talking about how best to learn from incidents, or how to foster psycological safety. Everything we’re still discussing is about growing as people and building strong teams and communities.

This is a talk that draws on my personal experiences in the DevOps community and through the pandemic to show how regardless of the technologies we’re using, our communities and practice developed under the DevOps banner are far more important than any specific technology we’ve worked with. It’ll touch on how the most important talk I’ve ever given was about being vulnerable in public about my mental health, how the people (and not any technology) I’ve met in DevOps have helped me the most through this global pandemic, and how building strong communities is the most important “yak shaving” we can do.

The real evergreen DevOps is people.

Who should use Kubernetes? Like, who is Kubernetes for? Kubernetes can be difficult to install and complicated to use and manage. What are the benefits of Kubernetes, and at what point do these benefits outweigh the operational complexity?

Join Whitney for a fun and fast-paced talk about the benefits and drawbacks of Kubernetes, and why the main advantage of Kubernetes adoption is not what you think!

Learn how Kubernetes adoption affects application development teams. We’ll cover the three most common strategies of app development I see from businesses adopting Kubernetes - local traditional development, local containerized development, and direct development on Kubernetes. While many of the core skills and work of software development teams remains the same, this session explores the relationship between Dev & Ops with Kubernetes in the mix, as well as the new tools application developers may need as your organization adopts Kubernetes.

In this panel, we’ll discuss and debate how developer communities have changed and evolved through the pandemic, and chat about the best ways to educate, inform, and entertain them in a remote-first world.

Note: This panel is exclusive to VIP ticket holders.