Auteur: Ted Vinke

This is part 5 of the series called “Functional Java by Example”. In previous part we stopped mutating our documents and returned copies of the data. Now, we need to move some I/O away.

This is part 4 of the series called “Functional Java by Example”. In previous part we talked a bit about side effects and I’d like to elaborate a bit more about how we can prevent having our data manipulated in unexpected ways by introducing immutability into our code.

This is part 3 of the series called “Functional Java by Example” and is a cross-post from my personal blog. The example I’m evolving in each part of the series is some kind of “feed handler” which processes documents. In previous parts I started with some original code and applied some refactorings to describe “what” instead of “how”. In order … Lees verder Functional Java by Example | Part 3 – Don’t Use Exceptions to Control Flow

This is part 2 of the series called “Functional Java by Example”. The example I’m evolving in each part of the series is some kind of “feed handler” which processes documents. In previous part I started with some original code and applied some refactorings to describe “what” instead of “how”. In order to help the code going forward, we need … Lees verder Functional Java by Example | Part 2 – Tell a Story

Functional Programming (FP) is about avoiding reassigning variables, avoiding mutable data structures, avoiding state and favoring functions all-the-way. What can we learn from FP if we would apply functional techniques to our everyday Java code? In this series called “Functional Java by Example” I will refactor in 8 installments an existing piece of code to see if I can reach … Lees verder Functional Java by Example | Part 1 – From Imperative to Declarative