I feel OO Design is more applicable to a wide variety of problems than OOP itself.

Actually, you could also learn a bit about UML, sort of OO way of thinking, without being language specifc (though Java is the most often used examples).

Unless you work on video game or missile guiding system, your analysis and design skills (i.e. knowing how to turn unorganized requests into actionable req spec into codeable design spec) are probably more important than your programming skill (as long as it's descent enough).

And the same old advice: practise. One hour of practice is better than 12 hours of reading. Solve some problems that interest you, be it making webpage or sorting through DNA.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.