Adrien Joly
Tech Coach @ SHODO
Paris, France
Actions
Based in Paris, France, Adrien Joly (he/him) started as a Software engineer in 2006. Ten years after writing his first Node.js-based full-stack web application (openwhyd.org), he's still maintaining it in production and using it to practice legacy code refactoring techniques. In March, 2020, Adrien joined the consulting agency SHODO to grow with a community of like-minded professionals and practice his skills as a Software Crafter and Tech Coach. You can follow Adrien and/or contact him on Twitter: @adrienjoly.
Links
Area of Expertise
Topics
Decommissioning a legacy module progressively, using AST traversal
Somewhere, deeply hidden in an old codebase, a module has become so buggy and nasty that no developer dares making any change to it. Actually, developers want to get rid of it, but a big part of the codebase is indirectly relying on it...
Can this story resolve to a happy ending? How to prevent the situation from getting worse, while developers keep adding features in the codebase?
What if AST (Abstract Syntax Tree) traversal was the key? Let's see how it can help us keep an eye on these dependencies, and prune them one by one, until the module is gone for good! 😌
Visualizing and untangling a "Big Ball of Mud"
When developers complain about the messiness of a codebase they're asked to maintain, chances are that they are dealing with a "Big Ball of Mud" or "Spaghetti code". This means that the codebase has grown into an uneven or chaotic structure of modules. This happens naturally on long-lasting codebases in which developers had to integrate evolutions quickly, and lacked time, skills and/or alignment with stakeholders.
How to visualize the structure (or lack thereof) of a codebase? How to detect problematic patterns? (E.g. circular dependencies, to name one of those) And how to fix these structural issues?
In this talk, we'll find answers to these questions by exploring an open source codebase and proposing possible remediation strategies.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top