Trackcing Data in Complex Java Code: A Functional Programming Approach, Part II l lucidchart.com 1 pughbri 10 years ago 0 comments
Validate Registration Emails in Real Time to Increase Sales l lucidchart.com 2 pughbri 10 years ago 2 comments
Improving Angular 2 Load Times and a 29KB Hello World App l lucidchart.com 6 pughbri 10 years ago 0 comments
Implementing a Bandit Algorithm in a Multiple-Payout Scenario l lucidchart.com 2 pughbri 10 years ago 0 comments
Who the Heck Wrote This? 3 Ways to Deal with Bad Code l lucidchart.com 12 pughbri 10 years ago 0 comments
Using Scala to handle exponential growth at a startup (part 2) l lucidchart.com 24 pughbri 13 years ago 11 comments
Our team has been able to come up to speed on Scala and get productive pretty quickly. Within a month, the team felt comfortable in Scala. Most team members read through Odersky's "Programming in Scala" book to get an overview of the language which was helpful. We've also had some team members go through the Coursera class.
Our experience is that there is a cost to Scala when it comes to new hires. Very few new hires have any meaningful Scala experience so they have to come up to speed on the language whereas with Java or PHP most new hires are already proficient in the language. In the end, however, we believe that the benefits of Scala, Play and Akka over the long term will outweigh the short term cost of training new hires. Even with our new hires, we find they are pretty comfortable and productive after a month of learning and using Scala.