How about everytime you fix bugs it only seems to introduce more bugs?

What if you could write the same code, no matter the paradigm (imperative, OOP, functional) in a manner where the code is easier to understand / debug and extend / change?

-We will be introducing functional pipelines, which some Clojure (or F#/Haskel) developers use every day, but are less known in the OOP world such as Java/C#. We will use the Either monad (we won’t talk about monads!) where it can return either a SuccesResponse or an ErrorResponse.

-We will be introducing code where there are 6 manners of solving the same problem, 3 are using pipelines and we will be leading the audience to conclude for themselves whether using pipelines improves the code or not.

This is the second in a series of workshops on Clojure. We'll be exploring the language further and as part of the Clojure roadtrip where we dive deep into the language. Last dates with the third workshops published soon!

-We recommend (but not mandatory) that you bring your laptop to practice.

-The workshop will be in English, but we can make explanations in Spanish / Catalan on specific topics for those that need it.

Hope to see you! :)