Error handling is an issue that often comes up in our reviews. Different programs have different goals with respect to error handling. In a simple script it might be acceptable to just crash if an error occurs. The techniques we are showing here are for high reliability programs, where we want to ensure we handle a selected set of errors.
Noel here with the first Underscore newsletter of 2015. In this edition I want to focus on two big changes we’re making to our training courses.
Since the beginning on the year we have been rebuilding the online version of Essential Scala around studio style learning. We delivered Essential Scala online last year, but found the result unsatisfactory. We taught the course in a similar way to our onsite version, and it didn’t survive the transition from face-to-face to online communication. We realised we needed to radically change the course to take advantage of the different medium. We are really excited by the result, and think it will offer a much better experience for our students.
It’s no secret that the computing industry in general, and the Scala community in particular, has an issue with diversity.
Last year we took a small step to improve the situation, with our diversity programme for Scala Exchange. This year we want to go further. We are starting by offering training at half price for diversity candidates.
Lift 2.6 is out. The announcement links to the tickets for the details. I count the changes from 2.5 to 2.6 as 321 commits from 25 people.
Here’s my personal selection of some of those changes.