Scala Teams is sponsoring
Scala Days 2026
October 12 and 13, Kulturbrauerei, Berlin. Our team is at the booth all conference. If you are hiring Scala engineers or thinking about how AI changes what a Scala team should look like, come talk to us in person.
Book Time With UsFind us at the booth
|
Meet Scala Teams
We're bringing several people from Scala Teams, so there's always someone free to talk shop or hiring.
|
We're here for real conversations
Bring us a hiring problem, a hard architecture question, or just curiosity about running a dedicated Scala team. We'll give you a straight answer.
|
Two days, easy to plan around
Book ahead below or just stop by. We're at the venue for the full conference, October 12 and 13.
|
Book a time to meet
Tell us a bit about what you're working on and when you'll be at the venue. We'll confirm a time to connect at the booth.
What we're watching at Scala Days 2026
This year's program is asking questions we deal with in production every day. Here's where we'll be sitting, and what we've seen so far.
Going to any of these? Find us after and tell us what you think, or grab time with us before the week fills up.
-
Putting AI agents on a leash
Can the type system decide what an AI agent is allowed to touch? Scala 3's capture checking is built to limit access to files, the network, and anything with side effects.
What we've seenIn finance, legal, and regulated work, a wrong change isn't a bug ticket. It's an incident. Guardrails that live in the compiler beat guardrails that live in a policy doc.
-
Where Scala wins, and where it doesn't
When AI writes the code, where does Scala really help, and where does it fall short?
What we've seenThe compiler catches a lot of what AI gets wrong before anyone reviews it. It won't catch a bad idea that type-checks. That's still a senior engineer's job.
-
Writing the spec before the code
Does writing a clear spec first make AI-built code easier to trust? More teams are trying workflows where the spec drives the build, with checks at every layer.
What we've seenThe better you define what "done" looks like, the less time you spend cleaning up after the AI. In Scala, the types are a big part of that spec.
-
Types that know the rules
What if the compiler could enforce your business rules, not just your types? Refinement types let you write rules like "this amount is never negative" right into the type.
What we've seenThis is still research, but it shows where Scala is headed. The more rules the compiler enforces, the more you can trust code you didn't write by hand.
-
The next step for the ecosystem
What changes when Scala's tooling gets faster? Scala 3.9 LTS, sbt 2.0, and Metals 2 all arrive this year, plus clearer paths for teams still on 3.3 LTS.
What we've seenFaster tooling means a faster feedback loop, and when AI writes more of the code, that loop is everything. Weighing an upgrade? We're happy to compare notes.
Going to any of these? Find us after and tell us what you think, or grab time with us before the week fills up.