OOP?

 I always find it interesting to share OOP concepts with developers that are brand new to the concepts.

Recently, after explaining how to achieve polymorphism through classes and interfaces, a student in one of my classes literally shouted out:  “Using OOP means I have to know what I am developing before I start coding.”  He said this as if this was a bad thing.  I raised an eyebrow and said “uh… yeah.”

It makes me wonder how many developers wander aimlessly in code ….

2 Comments

  • All that is true if you're working in a department that primarily designs software or even working on a big project. For most of my career, I've developed small projects that needed to be done quickly. I would love to have the time to hash out all the details up front. Hopefully OO will allow developers to convince management of the benefits of having to do the design up front. But I'm skeptical. If you're working for a department that doesn't really understand what you do, how do you convince them that adding design time (with no visible product) is good?

  • That's really fun because I think so many of us start out that way. No matter how many years ago it was, I remember concentrating on what I COULD do with code and doing it. Coding for the sake of code, not for the sake of the solution. Very interesting indeed.

Comments have been disabled for this content.