disqus_csSO65QyWR

Looks good, having trouble reading the writing though. Can we get it in PowerPoint format for download?

1 reply

jbrains

I can't give you PowerPoint, because I don't have it, but I will happily give you PDF. Wait 10 minutes.

1 reply

jbrains

Click the image to download a PDF.

disqus_Fvf3Ak5qxP

Thought-provoking. So does this mean that "XFactory" would eventually get renamed?

Similarly, does "increase duplication in names" mean e.g. that there are classes with names like "XWithY" and "XWithZ"? (Looking back to your post http://blog.thecodewhispere... )

1 reply

jbrains

Thank you, Luke. Yes, I do eventually (!) rename XFactory, if I don't manage to eliminate it altogether. I find that I only keep proper Abstract Factories (read GoF again), which often become toolkits. Now, "toolkit" remains a structural name, but it better describes the intent of one way to use it.

As for "increase duplication in names", it tends to happen more with methods than with classes. For example, related code gathers in a handful of methods whose names become similar: I call that removing duplication in code, and increasing duplication in names. The duplication in names comes from making the names more specific.

1 reply

disqus_Fvf3Ak5qxP

That makes sense, thanks.

jbrains

Also related: https://github.com/kerrizor... which automates detecting duplication of words within names of methods on the same class.