5 ms·

I love the Object Mentor guys' blog articles, but they get a new blog every 2 years so it's really hard to find their articles in one place. I remember reading

by tieTYT 13y ago

I love the Object Mentor guys' blog articles, but they get a new blog every 2 years so it's really hard to find their articles in one place. I remember reading one, I think by Michael Feathers, that was about how sometimes your code gets larger when you refactor and that's expected and good. He compared code to an orange. The rind is the class/method signatures. The pulp is the implementation. If the rind get larger by reducing the size and DRY violations of the pulp, you can consider that worthwhile. If anyone can find this article I'd be grateful. I haven't been able to track it down myself.

tbrownaw 13y ago
He compared code to an orange. The rind is the class/method signatures. The pulp is the implementation. If the rind get larger by reducing the size and DRY violations of the pulp, you can consider that worthwhile. That sounds very very wrong, as you're making your code's clients do more work / be more complex just so you can simplify your implementation.
- tieTYT 13y ago
  That's a huge assumption on your part. You should show me an example in code of what you think I'm saying.
  - tbrownaw 13y ago
    It sounded like you were saying that making your codes interface bigger in order to make your code's implementation smaller, is a Good Thing.
    - tieTYT 13y ago
      No, I'm saying if avoiding a DRY violation creates more methods/classes it's worth doing.