News for hackers. Stuff that matters.
Re:The Python Paradox Is Now the Scala Paradox (2009) by Roboprog on Saturday September 17, 2016 @03:00PM (#12521865)
Those are some good points. Sometimes, though, you come across some new tricks (perhaps not that new, but anyway) that you really wish your coworkers would get on board with.

E.g. - Our current big project at work uses a lot of Javascript. My coworkers are primarily die-hard Java developers (I know Java, but I don't "live" there...). As Douglas Crockford said in a presentation "[those people] will go to their graves, never knowing how miserable they were".

Rather than writing a bunch of classes with one meaningful method ("Executioner", anyone?), I would rather use FP / higher order functions techniques (e.g. - partial function application, such as in Ramda.js). Also, the idea of anything approaching metaprogramming is very scary to them, rather than pasting in many copies of the same stuff with minor variations. Perhaps it's ("custom") abstraction in general that is scary, since so little is documented in most industry standard practice code.

At what point do you ask your coworkers to realize that the eighties are over, and [static] OOP is not the one true hammer of sole best practice any more???

Re:The Python Paradox Is Now the Scala Paradox (2009) by Roboprog on Saturday September 17, 2016 @03:06PM (#12521893)
Further aside: it's funny that in popular use, "abstract" means "unintelligible", but in math, it means "well defined shorthand", for the purposes of making bigger problems approachable, at all.
Re:The Python Paradox Is Now the Scala Paradox (2009) by antod on Saturday September 17, 2016 @05:07PM (#12522452)
If you think abstract is bad - wait until you see what civil engineers think 'concrete' is!
Re:The Python Paradox Is Now the Scala Paradox (2009) by galdosdi on Monday September 19, 2016 @11:41AM (#12532261)
Oh, I agree that trying to write Java in JavaScript is frustrating. To be fair, JavaScript is a language that cries out for some kind of structure to be imposed upon it.
Re:The Python Paradox Is Now the Scala Paradox (2009) by Roboprog on Monday September 19, 2016 @12:14PM (#12532523)
Sure. Good luck getting the unwilling to follow the structure, though.
Re:The Python Paradox Is Now the Scala Paradox (2009) by galdosdi on Monday September 19, 2016 @05:50PM (#12535065)
I mean, it depends on the structure. Maybe a crummy one was chosen in your case. The fact that individual shops are rolling their own or choosing their own structure means on average they have a poorer one than a language that picks good defaults to begin with. But you have to pick something, or you'll have 6 developers doing 6 different things and nobody will be able to read anything