After many years using Java (and loving it), I discovered Scala, at DevoxxFR in 2012.
That was a blast.
Since then, I became rather obsessed with that language and sought every opportunity to learn more about it, and about FP in general.
I've learned what a monad is, and then I learned not to worry about what a monad is. I've learned about higher-kinded types and all sort of bizarre things that only people who knew SI-2712 by its number usually care about.
Now, I thrive to share my enthusiasm about Scala with more and more people, and to make more friends by not talking too much about monads.
Also, I wear suits.
Working with technologies that are not (yet) widely adopted is very exciting but can lead to disturbing side-effects. Being slightly ahead of the main adoption curve, you may end up as the most tenured expert in the room, while still feeling that you have so much yet to learn.
So how do you deal with that tension? How do you make your project succeed while still feeling you are just slightly less a noob than your coworkers?
Being a Scala developer for more than four years, I've been in that situation more than once. I had my share of successes and miserable failures, and I collected some valuable tips along the way, that I want to share with you during that presentation.
I may use a few examples of Scala code during the presentation, but I feel the tips I present are not specific to Scala per se.
**SPOILER ALERT** : for illustration purposes, I might use pictures taken from a famous HBO tv show (the one where beloved characters face premature death), these may constitute spoilers for people having not watched it yet.