C# and object oriented language

Form knowledge point of view, i want to know that what is the best way to improve OOP concepts and its implementation.
I am learning C# and OOP since last 4 years but still feel less griping

Where and what to start for improve my skills in c# or OOP skills?

I found that my OOPS skills improved greatly when I studied design patterns -- not just due to the patterns themselves, but seeing their general approaches they use when creating the patterns.

For example interface-based polymorphism and encapsulation rather than inheritance are shown to a great degree in design patterns. These are good OOP principles that I felt I only fully understood once I'd seen them used.

Additionally, just reading a lot of other people's code is a good way to see OOP in action -- especially if someone points you to good examples.

Herbie

5 hours ago, Amit28 wrote

Where and what to start for improve my skills in c# or OOP skills?

Write software.

Find a problem in your life you can fix through software - and then develop that solution. As you add functionality to your modest program you'll find yourself moving away from simplistic constructs to more elaborate design patterns and practices.

Thanks for revert Herbie. I really feel the same. But i tried many time to learn DP but feel somewhat complicated description in mentioned site (design patterns) .

 DO know some source having plain and simple explanation of DP.

 Thanks again.

@W3bbo: Absolutely i agree with ur words.
Thanks

18 hours ago, Amit28 wrote

@W3bbo: Absolutely i agree with ur words.
Thanks

In my experience, design patterns are more useful after you've grasped the basics of OOP, which you have to do yourself by writing software.

Design patterns really come into their own when you start having to develop software which uses libraries that your colleagues haven't built yet.

This is the learning cycle that I've seen lots of people take:

• To start off with, they write horrendously complicated, super-indented stuff all in the Main function
• As they get better, they factor this into lots of static methods
• As they get better they start pushing lots of these methods into classes, and start being more "object orientated"
• As their projects get even bigger, and as they start other projects which have similar requirements, they start pushing stuff out into libraries
• When you get two or more libraries providing similar functionality which the consumer of the class doesn't care about, suddenly you discover that interfaces are a really good thing.
• If they start working in a team and suddenly not only need to make software that works, but software that is maintainable and can be made quickly, suddenly design patterns come into their own - they allow you to spend more time writing code and less time making sure your code doesn't introduce breaking changes which require meetings to resolve.

@evildictaitor:Wonderful step by step explanation. Me too feel its time to learn patterns. Does anyone know the good links,book or eBook for DP. I really need some source having simple and plain description of DP.

Thanks evildicaitor.

10 hours ago, Amit28 wrote

@evildictaitor:Wonderful step by step explanation. Me too feel its time to learn patterns. Does anyone know the good links,book or eBook for DP. I really need some source having simple and plain description of DP.

Thanks evildicaitor.

Whilst I recommend the GoF Design Patterns book - it is not intended for beginners to OOP - it's written in a very formal style and expects a working knowledge of OOP in C++ (or Smalltalk).

@Amit28: Head First Design Patterns is going to be your best bet; http://www.amazon.com/First-Design-Patterns-Elisabeth-Freeman/dp/0596007124/ref=sr_1_sc_1?ie=UTF8&qid=1324308922&sr=8-1-spell

10 hours ago, CaRDiaK wrote

@Amit28: Head First Design Patterns is going to be your best bet; http://www.amazon.com/First-Design-Patterns-Elisabeth-Freeman/dp/0596007124/ref=sr_1_sc_1?ie=UTF8&qid=1324308922&sr=8-1-spell

I'm finding it hard to trust a book where the cover art is the same as a Vagisil pamphlet.

1 day ago, W3bbo wrote

*snip*

I'm finding it hard to trust a book where the cover art is the same as a Vagisil pamphlet.

That is funny, but hardly a good reason to discount the book. The photo is probably sold in a general purpose collection, along with a bunch of people in suits crowding around a computer.

hey,, you can't judge whole things with some couple of negative points.. I have already post my order for head first book. Will definitely get back with my reviews about book.

Anyway thanks all..

@Amit28: Enjoy the book, but I'd keep in mind the possibility that you may be missing the proverbial forest for the trees. I'd take a detour and look at C++ AMP and GPGPU. The OOP will likely come back around and take hold in the end.  When it does we'll call it GOOP.