Do you find constantly rebuilding things that don’t need rebuilding? If yes, this talk is for you. The way your codebase is structured impacts what you need to rebuild after each commit, therefore, the codebase needs to be re-architectured with the build pipeline in mind. Sometimes you’ll have many responsibilities packed in one module, so you rebuild all of them every time you change one. Or maybe you have a multi-tiered application and adding a feature implies modifying (and rebuilding) all tiers, with cascading effects. In this talk we’ll go over scenarios like this and others, showing how the code can be rewritten in a way that minimises unnecessary rebuilds.
Required audience experience
Developers need to have significant refactoring skills to be able to benefit from this content
Objective of the talk
The main objective of this talk is to provide a number of patterns to easily restructure a codebase so a to make it more efficient to build, but without impeding normal development. The idea is that teams should be able restructure their application while still performing normal work.
You can view Abraham’s slides below:
You can view the session below: