Skip to content

Commit 765c57c

Browse files
authored
Merge branch 'main' into main
2 parents 6435d0e + 8b65553 commit 765c57c

File tree

567 files changed

+4696
-740
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

567 files changed

+4696
-740
lines changed
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
+++
2+
Title = "Program"
3+
Type = "program"
4+
Description = "Program for devopsdays Atlanta 2023"
5+
Icons = "false"
6+
+++
7+
<div class = "row">
8+
<div class = "col">
9+
If Open Space is new to you, you may be interested in <a href="/pages/open-space-format">more details about Open Space</a>.
10+
<hr />
11+
<i>All times are in US Eastern Time</i>
12+
</div>
13+
</div>
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
+++
2+
Title = "What RomComs didn't teach me about Incident Management"
3+
Type = "talk"
4+
Speakers = ["ajuna-kyaruzi"]
5+
sharing_image = "ajuna-kyaruzi.jpg"
6+
+++
7+
RomComs are beautifully hilarious in the way they actively misunderstand each other at any given moment and formulaic to a fault. Incidents are not.
8+
9+
As an avid reader and consumer of romantic stories and a former SRE, I’ll go over what not to do in incidents from watching way too many RomComs.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
+++
2+
Title = "Panel: Privacy litigation related to tracking pixels, session replay, and chatbots on websites"
3+
Type = "talk"
4+
Speakers = ["brandy-griffin","lynn-sessions","paul-karlsgodt"]
5+
sharing_image = "brandy-griffin.jpg"
6+
+++
7+
We will discuss the growing area of privacy litigation surrounding the use of tracking pixels, session replay, and chatbots that are triggering legal claims based on various privacy laws. The panel will highlight current litigation and losses in this area while also providing insights into best practices to reduce an organization’s legal exposure. Web developers, marketing teams, and technology executives should understand the privacy risks involved when implementing these solutions.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
+++
2+
Title = "The 7 Horses of Abductive Reasoning"
3+
Type = "talk"
4+
Speakers = ["chris-corriere"]
5+
sharing_image = "chris-corriere.jpg"
6+
+++
7+
This talk starts with a story about a farmer that doesn't believe in hierarchy and a socialite that aims to prove them wrong. We come to see how to leverage flatter ontologies in complex domains in an effort to foster collaboration.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
+++
2+
Title = "Buried in Technical Debt?"
3+
Type = "talk"
4+
Speakers = ["chris-stone"]
5+
sharing_image = "chris-stone.jpg"
6+
+++
7+
When software teams take shortcuts to complete tasks, assuring themselves that they will go back and improve things later when they have more time, they call this "technical debt," and many teams believe they have accrued too much. Learn about some of the ways this can happen and how teams can take action to start paying down that debt and get control of their projects.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
+++
2+
Title = "Thiving in Minimum Viability: The Adaptive Approach"
3+
Type = "talk"
4+
Speakers = ["eb-ikonne"]
5+
sharing_image = "eb-ikonne.jpg"
6+
+++
7+
In a rapidly changing world, traditional strategies are often insufficient to ensure success. Welcome to "Thriving in Minimum Viability: The Adaptive Approach," a talk centered on providing individuals and teams with techniques to not only survive but flourish in dynamic environments.
8+
9+
Change can come swiftly and unexpectedly, challenging the very foundations of established norms. To navigate this unpredictable landscape, embracing an adaptive approach is essential. This engaging talk delves into the concept of "minimum viability," where the focus shifts from perfection to iteration, from rigidity to flexibility, and from conventional to innovative and fostering the conditions that enable this.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
+++
2+
Title = "Reducing Trauma in Production with SLOs and Chaos Engineering"
3+
Type = "talk"
4+
Speakers = ["julie-gunderson","mandi-walls"]
5+
sharing_image = "julie-gunderson.jpg"
6+
+++
7+
Customer experience is the responsibility of the entire team. Many organizations leave reliability up to the SRE team, however reliability should be built in from the very beginning. In this talk, We will discuss what Service Levels Objectives are, why they are important to the organization, and how to define and set them. Going beyond SLOs, attendees will learn what Chaos Engineering is and practical ways to ensure compliance and resilience with best practices. We’ll show you how to focus your goals and error budgets with examples that will lead to reliability and improved user experience.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
+++
2+
Title = "Breeding 10x Developers with Developer Productivity Engineering"
3+
Type = "talk"
4+
Speakers = ["justin-reock"]
5+
sharing_image = "justin-reock.jpg"
6+
+++
7+
Sasquatch. Yeti. The Loch Ness Monster. The 10x Developer. You may think of these as mythical creatures that can’t possibly exist, but the 10x Organization is very real. In this session, Gradle’s Justin Reock will explain how a dedicated Developer Productivity Engineering (DPE) organization can breed 10x Developers. By reducing the toil, friction, and frustration of slow builds, flaky tests, and other avoidable failures, a DPE team enables a level of developer productivity that you may have thought impossible. Justin will help you explore DPE technologies, including build and test acceleration, failure analytics, and easily analyzed build records to show how to create an environment in which 10x Developers not only exist, but thrive.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
+++
2+
Title = "Looking ahead using Wardley Mapping"
3+
Type = "talk"
4+
Speakers = ["mike-clement"]
5+
sharing_image = "mike-clement.jpg"
6+
+++
7+
In a company, department, or team, we will often talk about “strategy”. This term is rarely well defined, or at least not defined in a way that is useful. It usually means that we need to see into the future to outmaneuver our competition, or at least to navigate a changing market and competitive landscape. Traditional tools are limited in their ability to help us which led Simon Wardley to create maps that have helped him (and now others) to understand the current landscape as well as see common patterns that can allow you to “predict the future”.
8+
9+
In this session, Mike introduces Wardley Maps, the different ways they can be used for understanding the strategic landscape, and aid in strategic decision making.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
+++
2+
Title = "Nameless Kubernetes Clusters. This is the Way."
3+
Type = "talk"
4+
Speakers = ["nicholas-eberts"]
5+
sharing_image = "nicholas-eberts.jpg"
6+
+++
7+
Whoops! You didn’t REALLY know the consequences of your decisions when you created that cluster, and now it will be your life-long friend. So you are stuck with a super popular CIDR range, that CNI you thought you loved turned out to be way too chatty, and the Kubernetes version you are running is no longer for this world. Fear not, there are steps you can take to separate the cluster from your platform. This talk is going to focus on some steps that will keep you out of a long term commitment with your Clusters. * Automate your infrastructure. * Flatten your network across all clusters. * Make services discoverable across clusters. * Define Cluster Types with labels and a Cluster Registry. * Establish Trust with a Unified Identity Provider. * Centralize Security and Policy configs.

0 commit comments

Comments
 (0)