If you’re working on a project that has been around for a while, chances are there’s a few cobwebs 🕸 on some parts of your codebase that make you cringe… This is a totally normal part of the natural growth of an application. But how can we improve our software and correct past mistakes in a sustainable way, and without massively blowing out the scope? 🤔 Let’s discuss an incremental approach to dealing with mature codebases! We will take some ideas from genetic 🧬 algorithms and micro-service architectures, and combine them with code analysis and snapshot 📸 testing, and look at a pragmatic, evolutionary approach to codebase health and maintenance.


Comments are closed.

Very interesting! Thanks Craig!!

Great Talk, but not directly relate to Angular

Not exactly related to Angular, but it seems a very nice tool anyway.

Interesting topics.