A maze of twisty classes
Jeremy Zawodny is starting to understand the goods and the bads of
a OO language like Java.
The downside is that folks can get carried away,
building so much structure that the real workings of a system end
up obscured and hidden behind so many layers of indirection and
abstraction. It makes my head hurt a bit. I’ve spent a bit of time
manually drawing out some inheritance diagrams (anyone have a free
tool to automate it) based on reading the code and associate
javadocs.
This is something that happens frequently. I’ve seen code that is
impossible to understand because it is overdesigned. Code where
every object is based on an interface, which makes it very hard to
understand exactly what code is being executed.
I’ve spent a bit of time manually drawing out some
inheritance diagrams (anyone have a free tool to automate it) based
on reading the code and associate javadocs.
You might want to give
From
