hi , ms.jacquie barker , i hope can get some advice form you , i have use java for application develpoment almost 1 and half year , however, i feel that my understanding of oop still poor ...specially in design , i do read some book on design pattern ...but flankly ...sometimes i don't understand why and when we use interface n abstract class for example ...from expert view of you ...what should we concerntrate and gain fully understand on oop first before really go for design ..
in other word, what is most concern when we talking about object-oreinted programming [ July 13, 2005: Message edited by: Nakata kokuyo ]
Originally posted by Nakata kokuyo: what should we concerntrate and gain fully understand on oop first before really go for design ..
In my opinion, you should concentrate on getting *experience*. That is, practice, reflect, discuss.
What helped me most to begin understanding OO design is to read about and start practicing refactoring.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Diving into design patterns, or J2EE, or any relatively advanced technology before understanding the fundamentals of objects is like trying to cook a gourmet meal before knowing how to boil water!
That's precisely why I wrote BJO -- to remedy what I felt was an "object crisis" developing in the industry.
The original "wave" of object orientation occurred in the early '90s, when many folks were rushing about, learning about the object paradigm and various OO modeling methods of the time (Booch, OMT, etc.) But, not everyone jumped on the OO bandwagon at that time.
Then, the initial Java "wave" occurred in the mid 90's, when early adopters got on board with the language. But again, not everyone jumped on that bandwagon, either.
Now, as organizations are standardizing on J2EE, folks are suddenly trying to play catch-up in a BIG way! Most folks try to dive directly into J2EE without a solid Java background, and if they are getting remedial Java training, it is often without a solid OO background. (Everyone is always focused on the leading edge ...)
I'm trying to help all of the many very talented IT professionals out there who are faced with getting caught up in a major way! Please consider B.J.O. to be an essential first read if you're fuzzy on OOP (or, if not a first read, then an important remedial read). I've gotten countless notes from readers who said that my book was the first to make sense after they'd read many other books/taken many other courses -- please see the reader reviews of my book on Amazon.com:
Beginning Java Objects by Jacquie Barker Average Customer Review: Usually ships in 24 hours
Yes i think so. ------------------------------------- And anthor books Head First Design Patterns by Elisabeth Freeman Head First Servlets & JSP by Bryan Basham Head First EJB (Brain-Friendly Study Guides; Enterprise JavaBeans) by Kathy Sierra Sun Certified Programmer & Developer for Java 2 Study Guide (Exam 310-035 & 310-027) by Kathy Sierra Java(tm)2: A Beginner's Guide by Herbert Schildt Code Complete, Second Edition by Steve McConnell
is Ok too. --------------------------------------------------- :roll: Anything else? may i help U ?
[ July 13, 2005: Message edited by: Jack The Ripper ] [ July 13, 2005: Message edited by: Jack The Ripper ]