Interview with Camille Fournier on rewriting software at GOTO Chicago 2014
The Interviewer
Mike Hall
Interviewer, community organizer at UGtastic
The Guest
Camille Fournier
Author of 'The Manager's Path' and Distributed Systems Architect
The Conversation
Mike Hall
Interviewer, community organizer at UGtastic
I'm sitting here with Camille Fournier. You're an expert in distributed systems and management. Today, you're talking about rewriting software. Why is it such a taboo?
Camille Fournier
Author of 'The Manager's Path' and Distributed Systems Architect
Rewriting is often seen as a failure of the original architecture. But sometimes, it's just the necessary evolution. The key is knowing *when* to rewrite versus when to refactor.
Mike Hall
Interviewer, community organizer at UGtastic
What's the signal that it's time to pull the plug?
Camille Fournier
Author of 'The Manager's Path' and Distributed Systems Architect
When the cost of maintenance—the sheer 'tax' on developer productivity—exceeds the cost of re-implementing. If your architecture is a barrier to every new feature, it's time.
Critical Insights
durable
"Technical rewrites should be treated as a strategic business decision based on the 'tax' of maintenance versus the cost of re-implementation, rather than a failure of original design."
durable
"Successful distributed systems require evolving the architecture alongside the business, not just scaling the existing code."