#83 Steve Elliot, When to Rearchitect

Summary
Steve Elliot, CEO of Agile Craft talks to me about re-architecting software, why it should be done, when to do it, and how to do it well.

Details
Who he is, what he does. When to re-architect, monitor usage patterns, out of date ui, spaghetti code, ratio of bug fixes to new code, not mobile enabled, difficulty recruiting, market opportunity. Making a decision, who gets a say. How to measure success on a long-term project. Practical steps for moving to new architecture. What to start with, easy or hard pieces; what to do next; how to keep the old system going. What about people who don't want to learn new things. Dealing with remote offices. How to keep the project on track and the momentum going.

Links
Agile Craft

Download mp3 of podcast

#2 Bob Downey, Software Development

Wide ranging discussion with Bob Downey of Galen Healthcare about software development practices, architecture, book theory vs practical considerations, refactoring in a business environment, how software grows, development and collaboration across multiple offices, promotion in development groups, decision making, technology choices, cloud platforms, keeping up with current frameworks, refactoring, reusability, testing, SpecFlow.

Book recommendations
Patterns of Enterprise Application Architecture, Code Complete 2, Refactoring: Improving the Design of Existing Code.

SQL Server 2012 Query Performance Tuning (Expert’s Voice in SQL Server), Dependency Injection in .NET, Pro .NET 4 Parallel Programming in C# (Expert’s Voice in .NET).