Have you ever written some boilerplate code for handling your application’s communication with the outside world? You know, that JSON (de)serializer that once was nicely generated at compile-time but broke when you had to evolve your business model?
Of course you have!
But there may be a way to abstract away this repetitive, low-value code that sneaks into every project. Maybe it can also allow for our business classes to evolve without breaking compatibility, while keeping the necessary boilerplate to a minimum. Maybe it would even give us many other cool things for free, far beyond mere serialization concerns.
Let’s find out!
YOU MAY ALSO LIKE:
The Last Frontier and Beyond
Valentin Kasas
Just a regular Scala developer with a necktie. Valentin has come a long way from C++ programming on little machines with 4 MB of unmanaged memory to big clusters with terabytes of RAM. Along the way, he progressively abandoned his old imperative habits to embrace the functional way—a journey that seems to never come to an end.