Java | Agile | Testing | REST | Go | ScalaThe Business Case for Functional ProgrammingSeptember 18, 2018
Neil Chaudhuri (He/Him)
Neil Chaudhuri (He/Him)
Functional programming isn't exactly a fun topic anywhere outside of technical conferences and The Big Bang Theory. Even software engineers who love code often tune out when they hear terms like monad and referential transparency. But if you are a technical manager or executive, heads up. Functional programming will limit your technical debt so you build better software faster than you imagined and will earn you the Tesla you always wanted.
Code Reuse For Real
Code reuse is a vision long offered by object-oriented (OO) languages like Java but has proven to be a myth--like the Fountain of Youth and fat-free ranch dressing that's edible. In practice OO languages tightly couple data with behavior, so it's hard to extract the behavior into reusable code others can use.
In functional programming (FP), behavior is the first-class citizen--in the form of functions that deterministically transform single inputs into single outputs. This empowers engineers to compose functions into data flows where providing data to an initial function sets off a Rube Goldberg machine where the output of that function becomes the input to the next function and so on down the line. You can also mix and match functions to create new data flows. In the end, building software is basically like building Legos. This makes your code easier to understand--or in FP vernacular, "reason about"--and makes code reuse a natural outcome of your day-to-day process.
Satisfaction Guaranteed. Literally.
If you manage OO projects, you may have heard of "design patterns," which came out of a book by a group of expert software engineers known as the "Gang of Four." Design patterns offer suggestions for modeling code that solves common problems in a manner resilient to change. In other words, thoughtfully applied patterns reduce your time to market so your team won't have to work the weekend after your mercurial client changes course. That spares you a lot of resentment and the cost of at least two pizzas--more if I am on your team.
Sounds great, right? It is! Sort of.
The problem is design patterns are opinion--expert opinion borne of decades of experience to be sure--but opinion nonetheless. As programming languages and technical challenges evolve, there is no way to know how well they will stand the test of time. The Singleton design pattern, for example, has been particularly controversial.
On the other hand, FP offers mathematical guarantees that the code you write is sound. The laws that govern it--Type theory and Category theory in particular--are not vulnerable to the whims of the broader technology landscape. Math isn't opinion.
This is why Elm developers often report
"0 runtime exceptions" in production, which sounds like
errors at runtime that would make
Sisyphus cry. That's a huge win, but note "0 runtime exceptions" isn't the same
as "0 bugs." No paradigm can guarantee that. FP can't stop a developer surviving on Red Bull after staying up all night playing
Fortnite from calculating the total price of a customer's shopping cart by subtracting rather than adding. Still, FP
--along with companion principles like immutability--
provides safeguards making it harder to write bugs and uncovers the ones your team does write more quickly and cheaply by virtue of
mathematical guarantees that endure.
More Quality in Less Time
That shopping cart bug should be caught by tests, but most software engineers look at unit and integration testing like flossing. They get why it's necessary but don't look forward to it at all. The consequences are particularly profound when leadership acts as an enabler. Not that you would ever do this, but many technology leaders find testing takes so long that they are satisfied with a few token tests. The result is illusory productivity. Delivering a mess of alpha- and beta-quality features quickly might impress unsuspecting clients at first, but watch their enthusiasm wane when the inevitability of bug fixes orders of magnitude more expensive becomes apparent.
To be fair, developer testing can be a pain. Test setup is slow because you need to mock or stub your inputs along with any dependencies necessary for the code to execute a scenario like databases or REST clients. This often requires an open-source library like Mockito or unittest.mock.
And you have to repeat this process for multiple happy-path scenarios and some arbitrary number of alternate-path and error scenarios.
And you need to write your tests efficiently so that the test suite doesn't take hours to run in continuous integration.
All of that is cumbersome, but FP can make it easier.
The first thing you should do--FP or not--is to reduce dependencies. Lots of dependencies is a smell. Then replace the remaining object dependencies with functional dependencies. Gradually have the engineers evolve their APIs towards behavior rather than objects.
For example, let's say one of your user stories involves fetching a username by an identifier to use it for subsequent business logic.
Typically, that code has a dependency on some object that knows how to read from the database. Testing the logic in isolation
requires the overhead of writing your own stub for that database object or importing a library to mock it. What if instead the
dependency was on a simple function that takes a number (the identifier) and returns a string (the username)? In Scala,
that might look like
Int => String. This
elegantly decouples the logic from the database concern or any particular family of objects; all it knows is
"If I give this function the right identifier, I get the username back." Even better, I can stub that function really easily:
- One happy path:
123 => "neil"
- One error path:
999 => throw new UserNotFoundException("No user with id 999")
That's really easy. No mocking libraries necessary. In production the logic will use a function performing the real database lookup, but it
will still have the identical
Int => String shape.
As for test inputs, consider property-based testing. For the cost of less initial setup than you do now for a single input, tools like ScalaCheck will generate literally hundreds of inputs that will put the code through the wringer against data you never imagined and would never have time to write yourself. I would suggest property-based tests as the first line of defense in development but conventional, scenario-based tests with functional dependencies to address bugs discovered in functional testing or production.
Finally, if your team's tests have sophisticated setup with expensive resources you'd like to share across tests and clean up afterwards, have your engineers employ the Loan Pattern, which is one of the FP-est things you can do. I wrote an example on Stack Overflow of how powerful this can be for testing Big Data jobs using Apache Spark.
Easier Than You Think
It is very likely that today you can begin to enjoy many of the FP advantages I've described. Most modern languages--even Java finally --offer some degree of FP either in the core language or through open-source extensions.
It is also critical to keep in mind that it isn't a zero-sum game among FP and other paradigms. In fact, the fundamental academic premise of Scala is that OO and FP can not only coexist but complement each other to produce an ideal language offering the best of both. Similarly, FP can complement other paradigms like the imperative, procedural philosophy that drives Go.
Consequently, you should not worry that FP demands a radical transformation of your code base that is unrealistic for your timeline and unthinkable for your client. No need to send everyone to Haskell training either.