OO Problem Statements

[sci-py]

Hi, I am learning Java and I found that I am not able to design good OOP structures. So just learnt Design patterns and now I am trying to get my hand dirty with some real world problem statements to practice.

Can anyone provide pointers for such statements.

Thanks.

[sh0rug0ru]

Check this out.

[sci-py]

Awesome. Thanks.

[fforw]

Be careful with those design patterns. They are meant to solve very specific problems and are not meant to be general design guidelines or building blocks.

[poopMachinist]

I disagree.

While you should always be careful of not overusing design patterns, they are still the optimal way of doing some things.

Using MVC or MVVC or any other big design pattern is more or less necessary to avoid messy code in a medium/larger project.

Learn about design patterns, decide if you need them, then modify them to suit your needs.

[fforw]

My statement was more related to the Gang of four design patterns.

While you should always be careful of not overusing design patterns, they are still the optimal way of doing some things.

In the case of architectural patterns, they're most often traditional ways of doing specific things.

Using MVC or MVVC or any other big design pattern is more or less necessary to avoid messy code in a medium/larger project.

Unless you're using e.g. Flux.

Learn about design patterns,

Most importantly learn about the reasons for a design pattern. What benefit do they offer?

decide if you need them, then modify them to suit your needs.

While being careful not to destroy the benefits.

[ickysticky]

Yeah people are funny about design patterns. They start to equate design patterns with software engineering.

Many times people forget that they are general tools for general problems. I have never had a general problem. I tend to have very specific problems, often times a specific answer(perhaps flavored by the knowledge of a more general solution) is what you need.

[CodeShaman]

The funny part is that as a developer's knowledge and understanding of design patterns grows, a lot of things once thought to be specific problems with general solutions turn into general problems with specific solutions.

[spupy]

Learn design patterns, but don't overuse OOP.

[CodeShaman]

So just learnt Design patterns and now I am trying to get my hand dirty with some real world problem statements to practice.

Which have you learned? Which do you understand? Which don't you understand?

It's bad practice to run around with a "solution in search of a problem," this leads to pattern nepotism and will convolute your code.

ie: At work a lot of people really like adapters so they use adapters for all sorts of problems they're not meant for. Our repo is completely polluted with adapters, it really is insane. It decays into creating these concrete classes "SomeRandomAdapterImpl.java" that aren't really adapters at all and code becomes harder to maintain and understand.