A copy paste chapter - I almost feel that I should a previous post, just to stay on theme.
The different phases have different purposes. They call for different styles of solution, different aesthetic viewpoints.
In this case: copy-and-hack is an option. OK, that doesn't bother me too much. Why copy and hack instead of some other idea and hack? Well, it's easy to type? I suppose that's reason enough.
If we weren't willing to copy-and-hack, I suppose the alternatives would be to refactor toward a more flexible design first, then leverage that into a more dignified introduction of the new functionality.
It's probably also worth noting that one reason copy-and-hack is a wall clock fast option: there's not a lot of code here yet - less than 15 lines if we are willing to ignore the white space. So 10 out of 10 for changing course while it's still easy to do.
I think the "eliminate duplication" message would be stronger if it didn't carry over from chapter to chapter.
No comments:
Post a Comment