3 ms·
I am terrified of working with experienced Scala developers. The code they write is less about implementing some business functionality in the most elegant way
by threeseed 10y ago
I am terrified of working with experienced Scala developers.
The code they write is less about implementing some business functionality in the most elegant way possible. But rather it's an exercise in who can use the most obscure parts of the language.
And unfortunately there are far too many obscure parts.
- premium-concern 10y agoI have never seen this.
- threeseed 10y agoThe levels of enlightenment: http://www.scala-lang.org/old/node/8610 http://www.scala-lang.org/old/node/8610 Most Scala developers are in the A bracket. The experts are in the L. The code written by either is so different they could almost be different languages. You don't get this sort of split in Swift, Java etc.
- premium-concern 10y agoThis is more of a split between techniques for programming-in-the-small vs. programming-in-the-large. All languages have this. You could write more or less the same list for Swift or Java with minimal changes. Again, do you have any actual experience with this, or is this just your assumption? Because I have never seen this issue in the wild.
- timv 10y agoI have absolutely seen it in the wild, but at least in my case it seemed to be more a case of "People who wish they were writing Haskell, but found more commercial opportunities with Scala" compared with "People who found Scala to be an improvement over Java". At the extreme of the first group you'd have people for whom it seemed like every problem was best solved with a higher-kinded-type. And while it might well have been technically (and mathematically) elegant, the rest of the team was left scratching their heads trying to understand it.
- naasking 10y ago> The code they write is less about implementing some business functionality in the most elegant way possible. But rather it's an exercise in who can use the most obscure parts of the language. I think it's rather more likely that you simply don't understand why they're using the more obscure parts of the language on any given problem. They're probably trying to rule out certain invalid uses as type errors, which is typically encouraged in the more advanced typed languages.
- justinhj 10y agoI work with a team of 8 scala developers of varied experience. We try to set the bar at the sweet spot of power and readability. If someone's code becomes super dense because they've gone crazy with scalaz constructs then we ask at review stage to simplify, to comment and/or educate the rest of the team. I don't think experienced coders should be irresponsibly using Scala at a level that is inappropriate for the team.