If everyone agrees with you, you are probably not innovating, you are conforming faster. History’s real breakthroughs did not come from consensus but from heretics, hackers, and the endlessly curious. In this talk, Michael Carducci challenges the myth of collective wisdom and explains why the crowd is almost always optimized for the past. Through stories of unconventional thinkers, from computing pioneers to magicians who redefined wonder, he reveals the recurring patterns behind genuine innovation: discomfort, doubt, and persistence in the face of disbelief.

Attendees will learn how to identify the hidden forces that suppress new ideas, trust intuition even when it runs against consensus, and nurture the curiosity and courage that fuel meaningful change. This session is a call to those who question norms and experiment at the edges, the place where all real progress begins.

What You Will Learn

• Why consensus often inhibits innovation and creativity
• How to recognize and resist social and organizational forces that suppress new ideas
• Practical ways to cultivate curiosity, intuition, and courage in your work

Who Should Attend

Developers, innovators, leaders, and creators who challenge convention and seek to build ideas that move technology, and people, forward.

How we transformed a React monolith into multiple apps inside one codebase.

You always start small: one product, one team, one stakeholder. But once you succeed and need to scale, your original frontend architecture might not be ready for what comes next. As our Sales Process Orchestration Platform expanded to support multiple products and sales channels, our original monolithic application became a bottleneck.
In this talk, I'll share how we transitioned to a domain‑driven, multi‑app architecture while deliberately keeping a single React codebase. You'll see how we applied Domain‑Driven Design concepts on the frontend, structured clear boundaries between sales channels, and used Nx to orchestrate builds, enforce architecture rules, and keep teams moving independently without losing shared foundations.

"Write once, run everywhere" is a promising goal in software development, but one that often breaks down under real-world problems. At Zattoo, building streaming applications across Android, Apple, and Web meant years of separate native stacks that were not aligned, and therefore did not scale. This talk explains how moving to a multiplatform architecture, enabled by Vega as a fourth (React Native first platform), brought us very close to achieving that goal.

"Write once, run everywhere" is a promising goal in software development, but one that often breaks down under real-world problems. At Zattoo, building streaming applications across Android, Apple, and Web meant years of separate native stacks that were not aligned, and therefore did not scale. This talk explains how moving to a multiplatform architecture, enabled by Vega as a fourth (React Native first platform), brought us very close to achieving that goal.

React Native has changed a bunch, and if you haven't looked at it lately you're in for some fun. We'll walk through building a real app with (my beloved 😍) Expo. Talk about project setup to app store submission with detours into AI-assisted development and ofc, talk about the casual masochism that is mobile dev.

Vi på Sikt skriver skjemaet vårt først for deretter å koble dette opp mot våre datakilder. Dette er ganske enkelt og smertefritt, men hva gjør du når det dukker opp verbose mønster som GraphQL SDL ikke lar oss generalisere?

Kom og hør hvordan vi har løst dette ved hjelp av det jeg liker å kalle SDL-makroer eller schema transforms.

Hi. We will present an experimental IDE for navigating the ECMAScript specification document. The IDE provides a custom pseudocode notation that matches the look-and-feel of the ECMA-262 spec, and supports the usual features (outline view, go to definition, find usages, diff). We'll also demo functionality for advanced navigation and comprehension of pseudocode, such as pattern-based code search within the spec's algorithms, and local refactoring/modifying/annotating the spec for learning purposes.

⚠️ Content Warning ⚠️

Depression, dark thoughts, anxiety – These are some of the words that most of us would like to add to our ignore file. Discussing mental health is still taboo in our society, and it’s even more so in the developer ecosystem, where we pride ourselves on working long hours and our lack of sleep.

More than ever, we need to talk about mental health! This is why I want to share my experience with depression, general anxiety, ADHD, and experience volunteering at a suicide prevention hotline. Along with my thoughts on how we can improve the situation, I’ll be sharing some tips to help people be more open about these topics and issues – more importantly, I want to touch on how those struggling can ask for help and assistance when needed.

An opinion and methodologies on how to modernize an outdated and unmaintained codebase while at the same time delivering features. We will also explore how AI can support modernizing a legacy codebase.