[SP-2025] Add event date and cfp date #15070
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,23 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-12" | ||
| talk_start_time = "14:15" | ||
| talk_end_time = "14:20" | ||
| title = "Pipeline ETA: 3… 2… Tomorrow? Let’s Fix That!" | ||
| type = "talk" | ||
| speakers = ["alexander-ptakhin"] | ||
| youtube = "VNcxlBU05l8" | ||
| vimeo = "1072657488" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Ignite | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| Alexander, a Berlin-based tech lead with experience from startups to big tech, is passionate about optimizing processes for better product outcomes. |
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,25 +1,25 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-13" | ||
| talk_start_time = "12:00" | ||
| talk_end_time = "12:30" | ||
| title = "The Power of Simplicity: Crafting Durable Software Systems" | ||
| type = "talk" | ||
| speakers = ["bertrand-delacretaz"] | ||
| youtube = "_uLWfGWlKMc" | ||
| vimeo = "1072694682" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Talk | ||
|
|
||
| Simplicity often takes a back seat in software engineering. Yet, it's absolutely key for creating durable and efficient systems. | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| 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. |
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,21 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-12" | ||
| talk_start_time = "13:50" | ||
| talk_end_time = "13:55" | ||
| title = "Eating Your Own Dog Food - The Secret Sauce for Better Product Development" | ||
| type = "talk" | ||
| speakers = ["carmine-vassallo"] | ||
| youtube = "mXMjupehH1I" | ||
| vimeo = "1072682003" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Ignite | ||
|
|
||
| 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. | ||
|
|
||
| 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. |
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,23 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-12" | ||
| talk_start_time = "11:00" | ||
| talk_end_time = "11:30" | ||
| title = "Building Internal Platforms to Enhance Developer Experience" | ||
| type = "talk" | ||
| speakers = ["christina-kraus"] | ||
| youtube = "mcD2CjzT3C0" | ||
| vimeo = "1072677186" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Talk | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| 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. |
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,21 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-13" | ||
| talk_start_time = "14:15" | ||
| talk_end_time = "14:20" | ||
| title = "Tomorrow’s DevOps Engineers, Today!" | ||
| type = "talk" | ||
| speakers = ["daiany-palacios"] | ||
| youtube = "RDZAa-qEKgw" | ||
| vimeo = "1072695599" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Ignite | ||
|
|
||
| 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. | ||
| 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? | ||
| 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 |
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,27 +1,27 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-12" | ||
| talk_start_time = "11:30" | ||
| talk_end_time = "12:00" | ||
| title = "Pipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do" | ||
| type = "talk" | ||
| speakers = ["daniel-raniz-raneland"] | ||
| youtube = "loCqijMmVs0" | ||
| vimeo = "1072678729" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Talk | ||
|
|
||
| Automated pipelines have become an integral part of our daily workflow. As the pipelines become increasingly important, the demands placed on them rise proportionally. | ||
|
|
||
| As with many things, a great pipeline operates seamlessly in the background, while a poorly designed one becomes a constant irritation. | ||
|
|
||
| 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? | ||
|
|
||
| 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. | ||
|
|
||
| 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. |
|
Collaborator
There was a problem hiding this comment. This is a file of Zurich, not sure why you are modifying it here
Contributor
Author
There was a problem hiding this comment. There was an error in the merge from main. I'm going to cancel this PR and send another one. But I'll fix the errors pointed by you. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,21 @@ | ||
| +++ | ||
| City = "Zurich" | ||
| Year = "2025" | ||
| talk_date = "2025-03-13" | ||
| talk_start_time = "09:15" | ||
| talk_end_time = "10:00" | ||
| title = "Unintended consequences of well-meaning changes" | ||
| type = "talk" | ||
| speakers = ["dorota-parad"] | ||
| youtube = "pC9snEjTO7c" | ||
| vimeo = "1072666976" | ||
| speakerdeck = "" | ||
| slideshare = "" | ||
| slides = "" | ||
| +++ | ||
|
|
||
| ### Talk | ||
|
|
||
| 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. | ||
|
|
||
| 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. |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will only work if you set the
cfp_linkin themain.ymland you haven't done that yet