In the end, the code above is some pretty horrific and very optional suffering.
When I look at that code, I basically see a dislocated shoulder. A novice went to the gym and started trying to move the weights instead of exercise the muscle. Thinking in Java is a good book. No doubt about it. But to my taste, there is still a lot of "trying to move the weights" to it. There's too much about Java and not enough about thinking for a beginner. In the end, you don't need a book at all so much as you need to stop and REALLY, TRULY THINK about what you are doing and why. In my experience, very, very few people do this with any real regularity. In fact, it's not really a beginner problem. Even most of the very experience programmers I know don't do nearly enough of this. Particularly if what they are doing seems to be "working for them." But in the end, repeating what works is like moving the weights at the gym -- it's a trap and a good way to get injured -- and the only way out of that trap is to stay focused on incremental improvement of process. The master craftsman cares not so much about what is accomplished, but HOW it is accomplished. Truth is, you don't need my book. You can learn everything you need to know by reading this post a few times and taking it to heart. If you do, the shift in mind-set will be enormous. You will get stronger, much, much faster and you won't tear a rotator cuff like the guy above. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/ERROR-exceded-the-65-535-byte-limit-Please-Help-me-tp3041743p3041888.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
