Check out my kickstarter CLICK HERE
My book, my movies, my videos, my podcasts, my events ... the big collection of paul wheaton stuff!
Originally posted by Laojar Chuger:
Interesting! There is no answer for this beyond of textbook description. In the real world, everybody who writes C++/Java code declaims he/she is doing OO programming. However, the meaning of the OO is varying from person to person. What you actually see is they are using a difficult way to write C codes. Java is even worse if it is chosen. This leads to codes nobady can understand. Why? it loses the structure of the application in the name of OO. Good programmers write for the people, bad programmers write for the machine. If the machine can not understand, of course, it is not a programmer.
Uncontrolled vocabularies
"I try my best to make *all* my posts nice, even when I feel upset" -- Philippe Maquet
Take a Minute, Donate an Hour, Change a Life
http://www.ashanet.org/workanhour/2006/?r=Javaranch_ML&a=81
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Originally posted by Jerry Pulley:
Just got to chime in here...
refactoring...
So I'm going to twist the original question Tim asked just a little bit: I'll say the essential heart of OO development is building models - model the real world in your analysis, model the analysis in your design, model the design in your code. Whether working in Java or an assembler, the single critical thing that separates good programmers from average or worse is the ability to apply the appropriate level of abstraction to the problem in front of you today. The advance that OO brings, via languages and modern development practices, is a set of tools that lets people with this ability work magic.
Just my opinion, of course. I could be wrong...
Jerry
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |