Though correct this author makes a key assumption I dispute. "Scala as a better Java" === "people code in the same way in Scala & Java". This assumption leads to the focus on various Libraries and accepted standards.…
FYI -- Shameless self-interested hiring plug. Fintech startup nyc (Forbes 2016) https://www.dv01.co/. Excellent place to learn, good pay, fantastic city.
So, the takeaway is... hard work > IQ in influence. Sounds like shitty science wrapped up in nice language... booooooo
+1 This whole blog post reeks of elitism and over confidence. The blog post over states its own importance as after learning these clean code would be easy. Like fade diets, magic paradigms etc... another example of…
Whether you are dealing with OOP, functional, or some other pattern it is always the point to create abstractions which you and others can forget about how they work. Thus m->set_volume(.08) and set_volume(m, .08)…
The point is not a lack of objects but a lack of OOP. Yes, there are "objects" but there is also a separation between objects and methods etc.. The issue with m->set_volume(.08) is it becomes difficult to tell what…
Though correct this author makes a key assumption I dispute. "Scala as a better Java" === "people code in the same way in Scala & Java". This assumption leads to the focus on various Libraries and accepted standards.…
FYI -- Shameless self-interested hiring plug. Fintech startup nyc (Forbes 2016) https://www.dv01.co/. Excellent place to learn, good pay, fantastic city.
So, the takeaway is... hard work > IQ in influence. Sounds like shitty science wrapped up in nice language... booooooo
+1 This whole blog post reeks of elitism and over confidence. The blog post over states its own importance as after learning these clean code would be easy. Like fade diets, magic paradigms etc... another example of…
Whether you are dealing with OOP, functional, or some other pattern it is always the point to create abstractions which you and others can forget about how they work. Thus m->set_volume(.08) and set_volume(m, .08)…
The point is not a lack of objects but a lack of OOP. Yes, there are "objects" but there is also a separation between objects and methods etc.. The issue with m->set_volume(.08) is it becomes difficult to tell what…