in reply to Learning OOP
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.
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.
In Section
Meditations