Engineering
Architecture decisions and what they cost later, reliability work that kept a product up, migrations that finished, and the tools and habits that help a team ship often without breaking things.
Track hostDaniel ReisCTO, StackwellEngineering is the track for people who build and maintain the systems underneath a product. The talks lean towards the long view: decisions made three years ago and how they aged, incidents and what the review uncovered, and migrations described from the first ticket to the last deleted line.
It suits software engineers at every level, staff and principal engineers, and engineering managers who still read pull requests. Some sessions are marked Advanced in the schedule, but most assume only that you have shipped and supported something real.
Daniel Reis curated the track by favouring talks with a clear before and after, and by turning down anything that was mostly a product pitch.
Day 1Wednesday 9 June
Engineering· Talk · Intermediate
One database, four years, three migrations we regret
Lucas Moreau, Halden
10:30–11:10Studio
Engineering· Talk · Intermediate
Eight engineers, forty million requests: a case for boring architecture
Daniel Reis, Stackwell
14:30–15:10Main Stage
Engineering· Talk · Intermediate
Developer experience is measured in minutes to first deploy
Jonah Adeyemi, Stackwell
16:30–17:10Studio
Day 2Thursday 10 June
Engineering· Talk · Advanced
We deleted our single-page app and nobody noticed
Omar Saleh, Lumio
10:30–11:10Main Stage
Engineering· Workshop · Intermediate
Trace a real request end to end: observability from zero
Lucas Moreau, Halden
10:30–12:30Lab40 seats
Engineering· Talk · Intermediate
Your API reference is your onboarding: rewriting ours from scratch
Jonah Adeyemi, Stackwell
14:30–15:10Studio