Software Design X-Rays: Fix Technical Debt with Behavioral Code Analysis

On Thursday 24 May we'll start discussing Part II of Software Design X-Rays: Fix Technical Debt with Behavioral Code Analysis (https://pragprog.com/book/atevol/software-design-x-rays). If you have the book, read up through chapter 10. If not, come chat with us anyway!

As this meeting occurs during Ramadan I should note that it's pretty common for people to join our table without ordering food/drinks. Deli Boys is super friendly and has never tried to make every single person order. We welcome anyone interested in discussing computer science!

Are you working on a codebase where cost overruns, death marches, and heroic fights with legacy code monsters are the norm? Battle these adversaries with novel ways to identify and prioritize technical debt, based on behavioral data from how developers work with code. And that’s just for starters. Because good code involves social design, as well as technical design, you can find surprising dependencies between people and code to resolve coordination bottlenecks among teams. Best of all, the techniques build on behavioral data that you already have: your version-control system. Join the fight for better code!