Dealing with legacy code in Clojure


A view from the trenches: what we have learned by taking care of neglected Clojure microservices

When developing a new microservice in Clojure, do you think that the code being written might be maintained by someone else in the future? As a team created at Nubank to adopt cross-domain microservices that once belonged to other teams, here we will share some experience we gathered during the adoption process on how you can (re)write code that ages well and is maintenance friendly.


Isabella Pimentel (Nubank)
A software engineer who works at Nubank since the beginning of 2018. Graduated in computer engineering by the Polytechnic School of the University of Sao Paulo, online games made me choose this path after a frustrated attempt of studying mechanical engineering.Even when taking a long time to notice software engineering as a career path for me, computers were part of my life since my childhood, when I discovered their games, started playing with their configurations and elaborating simple web pages.I am a passionate learner and one of the things I enjoy the most is sharing knowledge with other people. My hobbies include fiction books, music, games, pets and the 2000s nostalgia.

Daouda Traore (Nubank)
Natural from Ivory Coast, a software engineer at Nubank since March 2019 and working to build and maintain microservices that attend common needs from engineers. Newbie in the functional programming world and impressed by Clojure effectiveness to get stuffs done.
Passionate trail runner, Daouda Traore has set the goal to become an ultra-marathoner.