TL;DR – Scala lets you expose internal data, then later change underpinnings while maintaining the same interface. The functional Way is an open Way. Internal data is available to anyone who wishes to extract it. “But what about encapsulation??” – horrified OO programmer“We do not fear your code, for you cannot screw up our immutable … Read moreData Exposure and Encapsulation
Quote: At first I wrote flexible code. I figured that because I couldn’t predict the future, I better leave all the options open. The code was modularized, well-factored, with a lot of bells and whistles, and more than enough documentation. I was proud of it, until I learned that: Things changed so rapidly that even … Read moreEvolution of a developer
Back in the Smalltalk days when OO was birthed, the idea was to have a bunch of objects that pass messages to each other. The focus was supposed to be on the messages. But people like objects. They are easy to draw on a white board. And they come with cool tools like inheritance and … Read moreTools vs Self-restraint, and a Dystopian vision of FP
Applicative functor: you wrap some food in a tortilla, you wrap the microwave in a tortilla, and you get hot food in a tortilla!— Jessica Kerr (@jessitron) September 10, 2013 But why would you do that?? Say you have a collection of document IDs and you are going to retrievethe documents from the database. Not … Read moreA realistic use case for applicative functors
If some team members use git-svn locally, they might have a local working branch. When the team moves to a central git repository, that work needs to come with them. In the old git-svn repo: 1) Find the revision where the local branch of interest branched off master: git svn find-rev `git merge-base $branch master` … Read moreConverting from svn to git: salvaging local branches