A Scala journey: from C# and front-end to the Typelevel stack
To mark Scala's 20th anniversary in 2024, Scala experts tell the stories of their own Scala journeys. This time: a junior developer from the London Scala community.
To mark Scala’s 20th anniversary in 2024, Scala experts tell the stories of their own Scala journeys. Get to know a junior developer who started with Scala in 2022.
How did you first get introduced to Scala, and what did you think about it?
I began learning Scala seriously in 2022, when I joined my current team in my first developer role after university. Before that, my software background was in C#, C++ and a bit of front-end technology. Moving into the world of functional programming was therefore not free of difficulties.
At first the learning curve felt quite steep; there was an enormous amount to grasp and plenty of confusing ideas I had to absorb rather fast. Gradually, though, writing Scala code started to make sense to me, and I have never regretted it!
How has Scala influenced your approach to solving programming problems?
I’d say what has shaped my problem-solving most is Scalas’ type system. In my experience, being able to count on it so reliably has been fantastic. When you do pattern matching, for instance, its exhaustivity tells you that every case is handled. That is the complete opposite of my front-end work in JavaScript, where you could only hope your code was right and discovered at runtime whether it actually was. Being confident about your code at compile time is much more pleasant.
Scala was my first contact with FP, so I can clearly tell where this paradigm’s influence on my coding style comes from. Breaking problems down into separate functions that you chain together, paying close attention to the input and output types, feels completely natural.
I also appreciate that Scala is not a strictly pure functional language: when imperative techniques are needed, it is flexible enough to let you use them, e.g., local mutability where that is the most sensible choice.
What is your favourite programming meme?
Honestly, this sums it all up…
What are your go-to tools and libraries when working as a software developer?
My development setup is IntelliJ with SBT.
The context actions are something really simple but so useful that I now depend on them. The ones I reach for most often are the type hints and the collection inspections.
In particular, when I chain many functions together, type hints keep me sane and focused on the actual problem. The collection inspections, in turn, are extremely useful because they suggest how to make code more readable and idiomatic, especially when I refactor code that got a bit messy while I was writing it.
As for libraries, my team relies mainly on the Typelevel ecosystem: Cats, Cats-Effect and Http4s among others.
How has the Scala community impacted your programming journey? Any standout interactions or support stories to share?
It is impossible to overstate how much the Scala community has influenced my learning so far. Right from my first weeks in my graduate role, the senior developers on my team supported and encouraged me. They put in the time and effort to prepare training materials, lead mob programming sessions and review PRs in depth. Without them, learning Scala would have looked completely different for me and would probably have been far less fun.
Beyond my job, people encouraged me to apply to conferences and talk about my experience as a junior developer. I used to think conference speaking was only for people with much more technical knowledge and development experience than me. That assumption turned out to be wrong. Going to conferences also got me involved in the London Scala community, which has been incredibly welcoming.
Joining an inclusive community that stresses how important it is to hear from every member, not only the most experienced ones, has been wonderful. And hopefully, thanks to that, we can learn how to make learning Scala a better experience for newcomers.
Special thanks go to my mentors for mentoring, supporting and encouraging me. My Scala experience so far would not have been the same without them!
Did you have any hilarious or embarrassing moments while learning Scala?
Oh, there have been lots of embarrassing moments in the short time I have worked with Scala. I have made many mistakes and asked plenty of painfully obvious questions, but everybody has been there at one point or another (or so I keep telling myself!).
What advice would you give to someone just starting with Scala?
A few things spring to mind.
First, if you are a junior developer, figure out which way of learning suits you – books, courses, or simply jumping into real-world examples. Knowing what helps you learn most effectively will make your life much easier.
Second, do not lose heart when things get tough and you feel stuck. That is exactly when you should turn to your community – colleagues, mentors or the broader Scala community. In my experience, people are usually very generous with their time and happy to pass on knowledge they worked hard for; you only have to ask.
Lastly, the Scala ecosystem has a lot to learn. Start by getting the fundamentals right. That will give you firm ground to stand on once you begin exploring all the great libraries out there.
How have you seen Scala evolve over the years, especially in your field of work?
Even though I have been writing Scala for only around 5% of its lifetime, there appears to be a growing emphasis on improving the developer experience. Scala is achieving this by making existing tools better and building new tooling that makes developers’ lives a bit easier, and by paying more attention to flattening the steep curve that comes with learning Scala.
What are your predictions for the future of Scala in the next decade?
To put it simply, since I am only starting my career, I have no idea what lies ahead for this language. What I do know, though, is how much I have enjoyed working in Scala so far and how much I would like to keep doing it for many years.