Estimate project
← All posts

A Scala journey – from a professor's tip to thinking in types

Find out how our guest began programming in Scala, how he reached the level he is at today, what he thinks about it, and more!

3 min read
scala20yearsofscalaFunctional Programming

Scala is turning 20 – let’s celebrate! Hats off to everyone who has contributed to the language and to all its fans – what a ride it has been!

We asked Scala experts to tell us about their Scala journeys. Our guest is a CTO and a content creator.

How did you first come across Scala, and what was your impression of it?

It was 2010, and back then I was working on my bachelor’s degree. One of my professors came across it and figured I would enjoy it. And wow, he could not have been more right.

Tell us about the moment you thought, “Aha! Scala is awesome!” Which features and capabilities of Scala gave you that feeling?

Although it was my professor who led me to Scala, I had read “Programming in Scala - Second Edition” before the semester began. That book made me see how much syntax matters in a programming language. Syntax is usually not treated as particularly important, but the book stressed that if the syntax leading to the best implementation is too clumsy, programmers may simply not choose that implementation. So a nice bit of syntax here and there may not change much, whereas syntax designed carefully from first principles will.

How has Scala shaped the way you tackle programming problems?

It was not an overnight change, but over the years it got me thinking more in types than in values. We don’t have to type everything to the limit, but reasoning in terms of types has definitely changed how I approach problems.

If you could add a new feature to Scala, what would it be, and how would developers benefit?

In my humble opinion, Scala is not in urgent need of yet another feature, but here goes. I really like exports in Scala 3. I only wish they produced less bytecode and let you export whole packages. That is not possible at the moment because of a limitation in the incremental compiler.

What is your favorite programming meme?

I have 2, and both have more to do with DevOps than with programming.

Image source

Which tools and libraries do you reach for first as a software developer?

libraries:

tools:

Tell us about a time when Scala turned out to be a game-changer in a real-world project

Nearly all of my experience, if not all of it, comes from startups that had picked Scala before I came on board. Still, I have seen one hobbyist developer build a Play app and keep it running in production for close to a decade with no clear sense of direction. It may sound like a cliché, but more than once he said something like, “if it compiled, I shipped it.” I’m paraphrasing, naturally.

Any funny or embarrassing moments while you were learning Scala?

I recall reading the chapter on partially applied functions in the “Programming in Scala” book more than 3 times, because I just couldn’t grasp them.

What would you tell someone who is just getting started with Scala?

Find a mentor, or at the very least stick to a set path, such as a book, a series of blog posts or videos, or a course. Scala is hard to pick up without guidance.

How have you watched Scala change over the years, particularly in your line of work?

Tooling has got enormously better (although there is still plenty of ground to cover). Remarkably powerful libraries have appeared. My personal programming style went from “FP solves problems that I don’t have” all the way to “FP solves all of my problems.” Scala 3 has its issues, but it feels like a real breath of fresh air.

Where do you see Scala heading over the next decade?

Being an optimist, I think Scala has a bright future. We still lean towards theoretical research, but in recent years the needle has been swinging towards the practical side. There is definitely plenty left to do, but we will get there.