Talks
What’s on stage at CPH Automate, with speaker details. Timeslots are placeholders until the schedule is finalized closer to the event.
Time TBA
JSON freedom or chaos; how to trust your data
Can you trust your data?
In this talk we'll take a real life use case where the flexibility desires and time have gotten the best of it. What happens when you deal with "freedom" data? How to go from this to a better future?
It is a technical talk how we recognise changes are desired, validation is required for trust to grow. Pydantic and pytest are used to work towards a solution where failing fast is a main objective.
Time TBA
What Should You Build When You Can Build Anything?
Being able to build almost anything does not make decisions easier. It creates more possibilities, and therefore more difficult choices. Every time we ask, "Should we build this?", we must also consider a "buy" option that AI is making better and faster.
Most discussions focus on how AI helps individuals build their own tools. But we speak less about what AI means for the vendors competing with these tools. This is also an important part of the build-versus-buy decision. AI is changing the capabilities of both internal teams and software vendors, so the comparison between them is changing as well.
In this talk, we will take a step back from the hype and consider what the software industry may look like after this transition. What will still be worth building ourselves? What will be better to buy? And what will be assembled from existing components?
We will explore these questions in the specific context of network automation. What do these changes mean for our industry, and how will AI affect what network automation teams choose to build, buy, or assemble from existing components?
The talk will not provide one answer that works for everyone.
Instead, it will offer a framework—and better questions—to help you decide what to build, what to buy, and what to combine.
Time TBA
When Your Source of Truth Isn’t Really Yours: Lessons from Cross-Team Integrations
What happens when another team integrates directly with your Source of Truth and their needs start limiting your ability to evolve your platform?
In this talk, I will share lessons learned from operating a Source of Truth that supported critical business processes while also serving as a dependency for another team through a complex, poorly documented integration. Because the integration was tightly coupled and the consuming team had different organizational priorities, even small improvements to data models, processes, and workflows became difficult to implement.
The session explores the challenges that arise when ownership, responsibilities, and priorities are not clearly separated between teams, and how these issues can slow down innovation and increase operational risk.
I will also discuss practical approaches that helped improve collaboration and reduce complexity, including:
– Creating simpler and more stable interfaces between teams
– Clearly documenting ownership, expectations, and integration contracts
– Implementing automated and continuous testing to detect breaking changes early
– Reducing coupling to enable independent evolution of systems and processes
Attendees will leave with actionable ideas for designing team boundaries and integrations that scale with both technical and organizational change.
Time TBA
Laziness. A Blessing or a Curse?
For decades we have discussed network automation, continually hoping the next tool or technology will solve it.
Perhaps the issue is not the technology at all. Maybe we are just lazy.
This speech questions a number of unpleasant assumptions concerning automation, AI, engineering culture and our obsession with the next exciting innovation.
This speech presents an uncomfortable examination of the reasons why we could be the main obstacle to network automation.