A Senior Software Developer at JetBrains, Justin believes in “Tools before Rules”: that is, automating the development toolchain to remove the pain of dealing with institutional processes. He’s on a mission to achieve this goal together with JetBrain’s IntelliJ Scala plugin team.
At Scala Days Lausanne, Justin will talk about the challenges developers face when integrating tools and how the Build Server Protocol makes it possible for IntelliJ to interface with any build tool. In advance of his talk Integrating Developer Experiences – Build Server Protocol we spoke to Justin about his journey to Scala, Scala’s biggest challenge developers are facing and why his role at JetBrains is his dream job.
Please tell us a little bit more about your role at JetBrain.
I have a dream job: I get to experience the fruits of the work I and my team put into our product every day developing Scala. We work on the Scala plugin for IntelliJ IDEA.
Why did you choose Scala and what kind of problems does it solve for you?
I wanted to get away from Java and it’s verbosity but still take advantage of a familiar ecosystem.
What is the most important challenge Scala developers are facing today?
Choosing and working with a plethora of tools available to create and deliver a product, and making them work together.
What is one thing that could address this challenge?
The Build Server Protocol is an approach that eases integration between build tools and IDEs. The same idea might apply to other levels of integration.
Who should attend your talk at Scala Days and why?
Anyone interested in improving the tools they use every day, but especially those involved in tooling.
Whom would you like to connect with at the conference?
Everyone! But especially our users and other tooling developers.