A Scala journey: a Lead Engineer's path into Scala
Discover how our guest began programming in Scala, how he got to where he is today, what he thinks about the language, and more!
In 2024 Scala turns 20! To celebrate, we asked Scala experts to tell us their Scala Stories. Our guest works as a Lead Engineer.
How did you first get introduced to Scala, and what did you think about it?
I first came across Scala at some point during high school, probably around 2014. It didn’t impress me much at the time, but I was still busy getting my head around Java and its modest functional programming features, so the paradigm shift took me a while ;)
Tell us about a moment when you realized, “Aha! Scala is awesome!” What Scala’s features and capabilities made you feel that way?
It happened when I saw just how expressive the language is, above all with its collections library. Even something simple, like walking through a list of numbers and applying a few transformations, turned out clean and easy! Things only got more exciting from there: pattern matching was like nothing I’d come across before, and higher-kinded types totally blew me away.
How has Scala influenced your approach to solving programming problems?
It certainly taught me to look at a problem from different angles. One of those angles is to identify a smaller problem, restate the larger one in its terms, and then solve the small one.
Scala made experimenting like this easy – thanks to the compact syntax and the absence of ceremony around defining datatypes, you can switch between different designs quickly.
If you could add a new feature to Scala, what would it be, and how would it benefit developers?
I’m not convinced Scala needs any new features. I’m quite satisfied with what’s already there, though I’d be glad to see a few of them improved. One example is named tuples (which are in progress!), and another would be tighter integration between opaque types and typeclass derivation (similar to Haskell’s GeneralizedNewtypeDeriving).
What is your favourite programming meme?
The one I share on the first working day of every January.
What are your go-to tools and libraries when working as a software developer?
- Tools: an editor that stays out of your way (Metals), a (decent) debugger (IntelliJ’s), and a quick feedback loop (automated tests and scala-cli scripts). I can’t get anything done if every attempt takes 5 minutes to try out!
- Libraries: it depends on the job, but I rarely go anywhere without Cats – I know that sooner or later I’ll need
Traverse.
Tell us about a time when Scala proved to be a game-changer in a real-world project.
Most likely the thousands of times it didn’t blow up.
How has the Scala community impacted your programming journey? Any standout interactions or support stories to share?
The Scala community has changed my life in ways I never would have expected. Even though I’m reserved and mostly introverted, this community made me feel welcome and helped me come out of my shell and actually enjoy meeting new people.
As soon as I could afford it, I began going to conferences and networking at every opportunity, and my only regret is that I didn’t do it more! Each conversation, be it in the hallways or at after parties, is an opportunity to learn and get inspired to build something new.
Over the years I’ve formed lasting relationships through in-person conferences, Twitter threads, and Spatial chats during the pandemic. Some of them became professional ties that led to job referrals or recommendations, while others widened my outlook. Traveling to conferences was particularly rewarding, as it let me meet people from other continents, backgrounds, and cultures and listen to their inspiring stories.
Did you have any hilarious or embarrassing moments while learning Scala?
Whenever I look at code I wrote a couple of years ago, I cringe – but I also appreciate how far I’ve come since then. Among other funny Scala-related moments, one that sticks out is bumping into another speaker by chance on a flight from Frankfurt to a conference in Boulder, US. And it wasn’t even the height of conference season!
What advice would you give to someone just starting with Scala?
Try it and stick with it. It’s a lifelong journey of constantly learning how to build excellent software!
How have you seen Scala evolve over the years, especially in your field of work?
Lately I’ve observed a welcome shift – believe it or not – toward stability. There used to be a new effect system every year, Scala 2 minor version upgrades caused a great deal of toil, and of course we kept hunting for the ideal JSON / HTTP libraries. These days, much of that churn seems to have disappeared.
In my area (distributed systems), we appear to have settled on one or two standard ways of architecting applications. People now understand that the HTTP or JSON library is usually not the bottleneck, which lets us concentrate on what our applications actually have to do.
Tooling went through a rough patch with the Scala 3 release that broke everything, but it now seems to be in good shape. The compiler offers completions quickly as you work on a problem, a new build tool no longer appears every month, and there are two dependable IDE options.
What are your predictions for the future of Scala in the next decade?
I’m hoping Scala 3 will become the industry standard. I’d love to see libraries move away from 2.x and make full use of Scala 3’s features. That would make them friendlier to use and would probably result in more libraries that solve common problems.
A lot of work has gone into making Scala easier to learn, with tools such as scala-cli, Scastie, and better documentation. These efforts should help draw in newcomers.
Whether or not Scala ends up as a top 10 language, it has left a lasting mark on me and rekindled my passion for programming. Scala isn’t going anywhere – it will remain part of our programming landscape, backing us up and paying our bills for a long time to come.