available at:
http://lsd.student.utwente.nl/jicarilla/TooMuchMagic
An essay that cautions us to keep our habit to outsmart ourselves in check.
please do tell me if I should stop advertising this stuff :D
- Leo
A more serious post than my last one (generally speaking--couldn't resist):
I don't know how you would fit it in to the structure of your essay, but the point I would like to make is that even though users expect a certain level of magic for the application to do for them, the developer doesn't have to use magic to implement it.
I suppose there are differing levels of magic.
I have a nightmare application at work here, and it appears that there was an over-use of collections magic. IOW, we can separate an inseprable junction between a screen and its document loading functions. If we have gone through the trouble of creating domain objects, why should you pass all the values in a Map that are part of that one object? Should you try to refactor, you can only get to the point where the application compiles again--then you have to run it to find all the ClassCastExceptions.
You are using too much magic if...
... you feel that java.lang.Object is the best way to pass information.
... you use collections to pass a bunch of information already available in one
object.--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
