... So Mr. Joe Average (J.A.) took that evening class in Java, read "Java in 24 hours" and took a position a couple of years ago in a soon-to-fail dot com. Joe was not much aware of OOP (or any formal approach), he only had his VB "experience" and short-lived affair with C/C++, but that was enough to pump up his courage to sprinkle syntactically correct combinations of Java keywords/identifier (e.g. "code") over a number of corporate software projects and create semi-functional applications. So, one day, J.A. had to work with the corporate RDBMS and he discovered (let's say) Hibernate (I mean he had enough with raw JDBC!). And he read there, that to make object persistent you have to provide setters/getters, so that Hibernate can persist them. Or, J.A headed full steam to implement an EJB/CMP2.0 solution, where all entity beans have to be a pointless abstract mess of get/set-ers. Or J.A used that stupid IDE, capable of generating bunch crappy classes full of getter/setter-s. Or, whatever ... At this point, the get/set thingy was well cemented in his not so big brain.
Since the project(s) were semi-functional (e.g. "successful"), J.A. decided he is a pro ( I mean PRO!). One day J.A reads this article form A. Hollub and wow!, his world is shattered, his (only) 2 brain cells agonize. Angered, J.A jumps on to the list and starts bashing the author of the article.
Now, J.A is finally satisfied:
"I made my point. After all, am I not a PRO? I will tell you, getter/setters...
Hani
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
