[whodatninja]

great read! I'm 3 years into the language and brought it into my company. As part of mentoring other devs coming from a web background, I kept repeating the mantra, "make it work the simplest way first" then explore the options scala gives you. As long as there were units tests for the logic, the details could change. The more I use the language, the more fascinated I become. Heck, I just learned about Bottom types last week!

[the_af]

I can see why you have this mantra, but doesn't this approach lead to programming in Scala as if it were Java (aka "you can program in Java in any language"), which results in unidiomatic code?

[Irish]

only if you believe the java way is the simplest way.....which I don't think is true

[the_af]

Good point! I absolutely agree with you, and it's very likely I've misread the parent post. It's just that sometimes I hear people at my workplace conflate "the simplest way" with "the way I'm more familiar with, coming from Java".

[whodatninja]

should have put an example to help clarify. For example, instead of throwing implicits around, i'd recommend they manually declare arguments like ExecutionContexts. Also sometimes the best way to teach someone from an OO background, is to first let them write their code imperatively, then work with them gradually to move to more functional approaches.

[Irish]

exactly, if its a java dev you are re-training their solutions will probably java in Scala, if its a javascript or haskell dev they would different probably. Whats interesting to me at least is if its someone with no previous experience.