Collective Code Ownership
I'm not afraid to change my own code. And it's all my own code.
As you work with code, you'll inevitably find that there's behavior you need on objects that you weren't planning to work on. You'll always find that there's commonality between what you're working on and some other object you weren't thinking about when you started. You'll always find behavior on one object that belongs somewhere else. You'll find objects that you were planning to work with that are recalcitrant, somehow resisting your attempts to use them. What should you do?
Well, if you owned those objects, you'd just fix them, wouldn't you? Yuck, this is wrong, you'd think. Let's fix it. Whack, wham, a little refactoring, and now it's all better. ...
Get Extreme Programming Installed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
