First Make It Correct
Starting out with a correct solution gave us clarity of thought about the problem, and a tangible way to test any other solutions that we can come up with. Property-based testing allowed us to maintain confidence even as we tried more and more daring approaches. Without the initial correct solution, none of this would be possible. Daniel Beskin |
Suspension: the magic behind composability (or: "The Kyo Monad")
Slides from LambdaDays 2025. Flavio Brasil (@flaviowbrasil) |
My experience migrating a PlayFramework app to Scala 3
Some interesting notes from the migration process. Tanin Na Nakorn (@tanin) |
Yet Another Scala 3 Migration Story
A rough summary of the experience of migrarting four services and one library, totaling more than 170k LOC. Voytek Pituła (@Krever01) |
How I disabled -Xfatal-warnings in IDE (IntelliJ) but kept it in CI
On one hand, it’s an inevitable PR review and code quality boost—I no longer have to comment on unused variables or imports. On the other hand, it kills experimentation and creativity. I’ve spent countless hours fixing unused variables and imports just to test something quickly. Łukasz Tymoszczuk |