What's so genius about this Martin Fowler?
I've been listening to some Java discussions and most topics are based "according to Martin Fowler" (duh!). But by reading his principles of code writing it's just an ordinary thing especially if you are a "progressive" Java Developer. Progressive in such a way that you have almost done everything, not tried, done.
For instance, this Inversion-of-Control/Dependency Injection(DI my ass!) pattern. Before that pattern got a name it has been used from the JVM far, far away. Even without a container. If anyone writing the same Java code over and over again for long years, definitely this buzzword will be such a hit and a welcome thing to the path of redemption from years of dirty, lousy code.
I think the only edge Martin Fowler has is his ability to write in muggle terms, which some of the equally or more talented Java people doesn't have.
For instance, this Inversion-of-Control/Dependency Injection(DI my ass!) pattern. Before that pattern got a name it has been used from the JVM far, far away. Even without a container. If anyone writing the same Java code over and over again for long years, definitely this buzzword will be such a hit and a welcome thing to the path of redemption from years of dirty, lousy code.
I think the only edge Martin Fowler has is his ability to write in muggle terms, which some of the equally or more talented Java people doesn't have.
Comments
Regards...