189 karma · joined October 26, 2011
You should read Java Concurrency in Practice, the entire book is explaining all the concurrency methods they have. And thats already a very good book (one of the top in my list). In Scala, I just need to read through a few pages of documentation and the rest is simply practice in mixing and matching patterns and a few configuration settings.
For a startup, you don't want to your programmers to learn cause its a heavy investment in terms of time. Adding and subtracting works just fine so they often advocate that route. You definitely get to the end goal, but when it comes to learning new things, you are never certain what the outcome will be.
For me Scala has a little bit more upfront cost to learning (but if you come form Java and C#, it should almost be second nature) but the things you can do with it once you get a hold of it is amazing. Go (for me) on the other hand is very easy to write simple Hello World programs, but if you want to do complex applications, it has much more down payment.
I am literally facing this at work. One of my colleague has an opinion on everything. Its quite frustrating because he is neither the most experienced person in the topic nor is he any good. I literally caught him using an if else statement for check whether a dictionary contained a key when one line would have done. Its programming 101, pick up a book and you will learn it in chapter 3. But he goes on saying he has 5 years in this industry... I am like okay bro. How he got a job is beyond me.
In the end, kindness is a tool in EQ. You should use it when needed and be stern when another approach calls for it. Hiding your dissatisfaction just to be kind will do the company long-term dis-service. Especially to the code base.