Skip to content

Commit ee1d15d

Browse files
committed
Merge branch 'main' into 2025-SP-add-date-cfp
1 parent 448ad00 commit ee1d15d

18 files changed

Lines changed: 395 additions & 395 deletions
Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-12"
5-
talk_start_time = "14:15"
6-
talk_end_time = "14:20"
7-
title = "Pipeline ETA: 3… 2… Tomorrow? Let’s Fix That!"
8-
type = "talk"
9-
speakers = ["alexander-ptakhin"]
10-
youtube = "VNcxlBU05l8"
11-
vimeo = "1072657488"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Ignite
18-
19-
Automated pipelines are essential for quality development, but what happens when they start slowing and frustrating us? We’ll explore strategies to minimize context switching and increase developer experience so we can stay in our flow and deliver joyfully.
20-
21-
The talk would be helpful for developers interacting with CI/CD and will cover decreasing pipeline length, local pipeline development, and execution without YAML spaghetti.
22-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-12"
5+
talk_start_time = "14:15"
6+
talk_end_time = "14:20"
7+
title = "Pipeline ETA: 3… 2… Tomorrow? Let’s Fix That!"
8+
type = "talk"
9+
speakers = ["alexander-ptakhin"]
10+
youtube = "VNcxlBU05l8"
11+
vimeo = "1072657488"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Ignite
18+
19+
Automated pipelines are essential for quality development, but what happens when they start slowing and frustrating us? We’ll explore strategies to minimize context switching and increase developer experience so we can stay in our flow and deliver joyfully.
20+
21+
The talk would be helpful for developers interacting with CI/CD and will cover decreasing pipeline length, local pipeline development, and execution without YAML spaghetti.
22+
2323
Alexander, a Berlin-based tech lead with experience from startups to big tech, is passionate about optimizing processes for better product outcomes.
Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-13"
5-
talk_start_time = "12:00"
6-
talk_end_time = "12:30"
7-
title = "The Power of Simplicity: Crafting Durable Software Systems"
8-
type = "talk"
9-
speakers = ["bertrand-delacretaz"]
10-
youtube = "_uLWfGWlKMc"
11-
vimeo = "1072694682"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Talk
18-
19-
Simplicity often takes a back seat in software engineering. Yet, it's absolutely key for creating durable and efficient systems.
20-
21-
Crafting simple software is hard and takes lots of efforts. It's about setting a high bar and persisting until the simplest solution emerges, which you can often tell by its beauty and efficiency.
22-
23-
This talk is based on more than twenty five years of software engineering experience, where the goal of essential simplicity has been reached in a few key projects. Digital audio recording, weather data management, interactive video kiosks, web app frameworks, the domains in which this happened are varied but a set of patterns emerges, that allowed us to reach high goals in terms of simplicity and efficiency in these projects.
24-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-13"
5+
talk_start_time = "12:00"
6+
talk_end_time = "12:30"
7+
title = "The Power of Simplicity: Crafting Durable Software Systems"
8+
type = "talk"
9+
speakers = ["bertrand-delacretaz"]
10+
youtube = "_uLWfGWlKMc"
11+
vimeo = "1072694682"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Talk
18+
19+
Simplicity often takes a back seat in software engineering. Yet, it's absolutely key for creating durable and efficient systems.
20+
21+
Crafting simple software is hard and takes lots of efforts. It's about setting a high bar and persisting until the simplest solution emerges, which you can often tell by its beauty and efficiency.
22+
23+
This talk is based on more than twenty five years of software engineering experience, where the goal of essential simplicity has been reached in a few key projects. Digital audio recording, weather data management, interactive video kiosks, web app frameworks, the domains in which this happened are varied but a set of patterns emerges, that allowed us to reach high goals in terms of simplicity and efficiency in these projects.
24+
2525
There's no magic formula for simplicity, but our real-world examples will help you discover principles and a philosophy of simplicity that will help on your own journey.
Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-12"
5-
talk_start_time = "13:50"
6-
talk_end_time = "13:55"
7-
title = "Eating Your Own Dog Food - The Secret Sauce for Better Product Development"
8-
type = "talk"
9-
speakers = ["carmine-vassallo"]
10-
youtube = "mXMjupehH1I"
11-
vimeo = "1072682003"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Ignite
18-
19-
What’s the best way to ensure your product truly delivers? Use it yourself. “Eating your own dog food” is more than just a quirky phrase—it’s a practice my team and I embrace every day. By actively using the products we build, we’ve uncovered hidden flaws, improved deployment strategies, and refined configurations based on real-world usage.
20-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-12"
5+
talk_start_time = "13:50"
6+
talk_end_time = "13:55"
7+
title = "Eating Your Own Dog Food - The Secret Sauce for Better Product Development"
8+
type = "talk"
9+
speakers = ["carmine-vassallo"]
10+
youtube = "mXMjupehH1I"
11+
vimeo = "1072682003"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Ignite
18+
19+
What’s the best way to ensure your product truly delivers? Use it yourself. “Eating your own dog food” is more than just a quirky phrase—it’s a practice my team and I embrace every day. By actively using the products we build, we’ve uncovered hidden flaws, improved deployment strategies, and refined configurations based on real-world usage.
20+
2121
In this talk, I’ll share how our team’s commitment to dogfooding has created a strong feedback loop that drives better decisions, builds confidence in new features, and enhances the user experience. Discover why living and breathing your product is the ultimate recipe for success.
Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-12"
5-
talk_start_time = "11:00"
6-
talk_end_time = "11:30"
7-
title = "Building Internal Platforms to Enhance Developer Experience"
8-
type = "talk"
9-
speakers = ["christina-kraus"]
10-
youtube = "mcD2CjzT3C0"
11-
vimeo = "1072677186"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Talk
18-
19-
Platform Engineering is one of the top trends in the cloud-native space right now. However, while the theory behind it is quite clear, implementations are still in their early days. We condense the learnings of our extensive platform building experiences across some of Germany's largest organizations into an informative session that will guide teams in their platform journey.
20-
21-
Platform Engineering is here to relieve developers from the ever increasing cognitive load as the cloud-native tooling landscape grows and DevOps practices or “Shift Left” approaches expand the scope of their responsibility.
22-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-12"
5+
talk_start_time = "11:00"
6+
talk_end_time = "11:30"
7+
title = "Building Internal Platforms to Enhance Developer Experience"
8+
type = "talk"
9+
speakers = ["christina-kraus"]
10+
youtube = "mcD2CjzT3C0"
11+
vimeo = "1072677186"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Talk
18+
19+
Platform Engineering is one of the top trends in the cloud-native space right now. However, while the theory behind it is quite clear, implementations are still in their early days. We condense the learnings of our extensive platform building experiences across some of Germany's largest organizations into an informative session that will guide teams in their platform journey.
20+
21+
Platform Engineering is here to relieve developers from the ever increasing cognitive load as the cloud-native tooling landscape grows and DevOps practices or “Shift Left” approaches expand the scope of their responsibility.
22+
2323
In this talk we’ll discuss how an internal platform can help you to effectively model the “new” responsibility split between developers and a platform team. We’ll talk about why developers as the internal “customers” of such platforms play a crucial role for its successful implementation and reveal typical pitfalls you should prevent on your road to a fully automated self-service developer experience.
Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-13"
5-
talk_start_time = "14:15"
6-
talk_end_time = "14:20"
7-
title = "Tomorrow’s DevOps Engineers, Today!"
8-
type = "talk"
9-
speakers = ["daiany-palacios"]
10-
youtube = "RDZAa-qEKgw"
11-
vimeo = "1072695599"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Ignite
18-
19-
More than 10 years into the DevOps movement, by now we know that it’s not just a job. We know the truth about DevOps (do we?) and understand that in principle there is not such a thing as a DevOps Engineer or a DevOps Team. Yet, our industry needed to find a label, a way to name the new role which Sysadmins or Developers were further growing into.
20-
Today, job ads for "DevOps Engineers" are everywhere, with diverse descriptions. I went through the hiring process for such a position in my team last year, and after interviewing a decent amount of candidates I started reflecting: How is this role going to evolve in the future? What about the next generation of “DevOps Engineers”? How do we get them “fresh” out of university”? How does someone come to the idea of starting their career in this field at all?
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-13"
5+
talk_start_time = "14:15"
6+
talk_end_time = "14:20"
7+
title = "Tomorrow’s DevOps Engineers, Today!"
8+
type = "talk"
9+
speakers = ["daiany-palacios"]
10+
youtube = "RDZAa-qEKgw"
11+
vimeo = "1072695599"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Ignite
18+
19+
More than 10 years into the DevOps movement, by now we know that it’s not just a job. We know the truth about DevOps (do we?) and understand that in principle there is not such a thing as a DevOps Engineer or a DevOps Team. Yet, our industry needed to find a label, a way to name the new role which Sysadmins or Developers were further growing into.
20+
Today, job ads for "DevOps Engineers" are everywhere, with diverse descriptions. I went through the hiring process for such a position in my team last year, and after interviewing a decent amount of candidates I started reflecting: How is this role going to evolve in the future? What about the next generation of “DevOps Engineers”? How do we get them “fresh” out of university”? How does someone come to the idea of starting their career in this field at all?
2121
In this ignite talk, I’ll share thoughts on nurturing the next generation of DevOps professionals. With patience, because we need tomorrow’s DevOps Engineers, today! :P
Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,27 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-12"
5-
talk_start_time = "11:30"
6-
talk_end_time = "12:00"
7-
title = "Pipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do"
8-
type = "talk"
9-
speakers = ["daniel-raniz-raneland"]
10-
youtube = "loCqijMmVs0"
11-
vimeo = "1072678729"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Talk
18-
19-
Automated pipelines have become an integral part of our daily workflow. As the pipelines become increasingly important, the demands placed on them rise proportionally.
20-
21-
As with many things, a great pipeline operates seamlessly in the background, while a poorly designed one becomes a constant irritation.
22-
23-
Are you publishing your artefacts every time the pipeline runs, running all steps in a sequence, or installing all the tools every time a new build starts?
24-
25-
In this talk, I will address these antipatterns and more I have encountered during my work as a consultant, explaining why I consider them such and what you should do instead.
26-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-12"
5+
talk_start_time = "11:30"
6+
talk_end_time = "12:00"
7+
title = "Pipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do"
8+
type = "talk"
9+
speakers = ["daniel-raniz-raneland"]
10+
youtube = "loCqijMmVs0"
11+
vimeo = "1072678729"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Talk
18+
19+
Automated pipelines have become an integral part of our daily workflow. As the pipelines become increasingly important, the demands placed on them rise proportionally.
20+
21+
As with many things, a great pipeline operates seamlessly in the background, while a poorly designed one becomes a constant irritation.
22+
23+
Are you publishing your artefacts every time the pipeline runs, running all steps in a sequence, or installing all the tools every time a new build starts?
24+
25+
In this talk, I will address these antipatterns and more I have encountered during my work as a consultant, explaining why I consider them such and what you should do instead.
26+
2727
After listening to this talk, you will better understand what makes a pipeline great and concrete things you can do to improve it and shorten the feedback loop.
Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-13"
5-
talk_start_time = "09:15"
6-
talk_end_time = "10:00"
7-
title = "Unintended consequences of well-meaning changes"
8-
type = "talk"
9-
speakers = ["dorota-parad"]
10-
youtube = "pC9snEjTO7c"
11-
vimeo = "1072666976"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Talk
18-
19-
As engineers, we’re used to thinking in algorithms where causality is clear and the same set of actions always produces the same results. When we apply algorithmic thinking to complex systems, however, our well-meaning actions often result in unintended consequences. Whether driving organizational change or fixing a small bug in your monitoring system, it’s not enough to consider the most immediate and direct result.
20-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-13"
5+
talk_start_time = "09:15"
6+
talk_end_time = "10:00"
7+
title = "Unintended consequences of well-meaning changes"
8+
type = "talk"
9+
speakers = ["dorota-parad"]
10+
youtube = "pC9snEjTO7c"
11+
vimeo = "1072666976"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Talk
18+
19+
As engineers, we’re used to thinking in algorithms where causality is clear and the same set of actions always produces the same results. When we apply algorithmic thinking to complex systems, however, our well-meaning actions often result in unintended consequences. Whether driving organizational change or fixing a small bug in your monitoring system, it’s not enough to consider the most immediate and direct result.
20+
2121
In this talk, I’ll go over examples of simple changes causing large scale unintended consequences, explain how to recognize when your actions could impact more than you wish for, share techniques for anticipating ripple effects so you can use them to your advantage, and help you become more adept at reasoning about complex systems.
Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
1-
+++
2-
City = "Zurich"
3-
Year = "2025"
4-
talk_date = "2025-03-13"
5-
talk_start_time = "14:20"
6-
talk_end_time = "14:25"
7-
title = "Software at Tesla - A peek from the outside"
8-
type = "talk"
9-
speakers = ["jonas-alder"]
10-
youtube = "Rcwjup8D8gE"
11-
vimeo = "1072696503"
12-
speakerdeck = ""
13-
slideshare = ""
14-
slides = ""
15-
+++
16-
17-
### Ignite
18-
19-
Tesla is arguably one of the hottest companies on the planet right now, with its ambitious goals and industry leading engineering & manufacturing capabilites. But how do they tackle software for their products and enterprise?
20-
21-
In this talk, I will share my insights and observations from following almost every move the company did publicly in the last century as well as using their products. Combined with my understanding and experience in the software world, I’ll highlight areas where their practices become visible to hopefully also spark your interest.
22-
1+
+++
2+
City = "Zurich"
3+
Year = "2025"
4+
talk_date = "2025-03-13"
5+
talk_start_time = "14:20"
6+
talk_end_time = "14:25"
7+
title = "Software at Tesla - A peek from the outside"
8+
type = "talk"
9+
speakers = ["jonas-alder"]
10+
youtube = "Rcwjup8D8gE"
11+
vimeo = "1072696503"
12+
speakerdeck = ""
13+
slideshare = ""
14+
slides = ""
15+
+++
16+
17+
### Ignite
18+
19+
Tesla is arguably one of the hottest companies on the planet right now, with its ambitious goals and industry leading engineering & manufacturing capabilites. But how do they tackle software for their products and enterprise?
20+
21+
In this talk, I will share my insights and observations from following almost every move the company did publicly in the last century as well as using their products. Combined with my understanding and experience in the software world, I’ll highlight areas where their practices become visible to hopefully also spark your interest.
22+
2323
As it will become strikingly apparent very quickly, Tesla has also taken software to the next level across their whole enterprise.

0 commit comments

Comments
 (0)