In recent months I have had the opportunity to work on the refactoring of a large legacy application, for a good part written in procedural code: the challenge was to make the application evolve to keep up with the business needs, without embark on an expensive and unthinkable rewrite During this session I'd like to share what techniques we used to achieve the goal, highlighting what worked well, and what didn't, to give you a couple more ideas the next time you're facing a similar challenge. Some of topics: - code organization from folder structure to classes - choosing an architectural style - testing - refactoring to objects


Comments are closed.

Great case study and a lot of tips about how to refactor a big monolith.

dParadiz at 20:21 on 12 May 2018

Missing some in-depth explanation of design choices.

Interesting approach to puzzle-refactor an applcation instead rebuild it from zero.

Gragio at 17:00 on 19 Jun 2018

I did not expect a tutorial. Very poor in theoretical concepts.

Michele Orselli (Speaker) at 17:30 on 19 Jun 2018

@Gragio, thanks for the feedback, I'm sorry the talk didn't meet your expectations. In my opinion the talk followed the description in the abstract: reporting some practical choices we made while refactoring a real application. So, no big surprises from this point of view. And you're right, there were no theoretical concept, I wasn't the point of the talk itself