Sign up to save your podcasts
Or
Share Large-Scale Refactorings | #48
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Large-Scale Refactorings | #48
First things first, "large scale refactoring" is really a colloquial expression, a shorthand we sometimes use, but in my experience there is no such thing, for two reasons. The first reason is definitional. Remember, refactoring doesn't mean "changing my design", it means "changing my design without changing its function". We almost never do this at large scale. The marvel and the horror of this trade is the extraordinary demand pressure it operates under. Anyone who's done time in the silicon mines knows this. It is the origin of nearly every bad process in the trade.
"Takin' it off, here, boss!" says Cool Hand Luke.
They pay us to change function. They don't pay us to change design, except in so much as it is required to transform function or to improve function-transformation process. So from a practical perspective, it basically just doesn't happen. One doesn't get large blocks of time where one is only transforming design, not function.
Episode 48 is live! If you are interested in becoming a part of the conversation, Click here to join the Change-Harvesting Camerata Today!
---
If you have any feedback you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. You can also read the full transcription of this podcast over on GeePawHill.org.
View all episodes
By GeePaw Hill
5
66 ratings
First things first, "large scale refactoring" is really a colloquial expression, a shorthand we sometimes use, but in my experience there is no such thing, for two reasons. The first reason is definitional. Remember, refactoring doesn't mean "changing my design", it means "changing my design without changing its function". We almost never do this at large scale. The marvel and the horror of this trade is the extraordinary demand pressure it operates under. Anyone who's done time in the silicon mines knows this. It is the origin of nearly every bad process in the trade.
"Takin' it off, here, boss!" says Cool Hand Luke.
They pay us to change function. They don't pay us to change design, except in so much as it is required to transform function or to improve function-transformation process. So from a practical perspective, it basically just doesn't happen. One doesn't get large blocks of time where one is only transforming design, not function.
Episode 48 is live! If you are interested in becoming a part of the conversation, Click here to join the Change-Harvesting Camerata Today!
---
If you have any feedback you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. You can also read the full transcription of this podcast over on GeePawHill.org.