DEV Community

Discussion on: Moving Past Tutorials: a course on problem solving for programmers

Collapse
 
aspittel profile image
Ali Spittel

Oh cool! I could totally write about design patterns in here. Thatโ€™s a great idea!

Collapse
 
johnsamuelob profile image
John Samuel Obinna

I can't wait for design pattern ๐Ÿ˜๐Ÿ˜

Collapse
 
kashperanto profile image
kashperanto

I agree for sure. Design patterns and other best-practices are often not fully appreciated by newcomers because most of the simple examples are not big or complex enough to show off why you might want to use something like object orientation, the state pattern, dependency injection, etc.

Collapse
 
cben profile image
Beni Cherniavsky-Paskin

When exposing beginners to design patterns, it's important to tell them specific patterns are language-dependent. Many have more idiomatic solutions in some languages, or solve problems some languages don't have (or refuse to acknowledge as problems worth solving).

It's easy to hear about a pattern as "here is a good way to code" and try to use it everywhere. But a pattern has 2 parts: problem & solution, and one has to understand the problem first.

I think the specific patterns in the GoF book were Java-centric (?), although their deeper legacy was to show an organized way to talk about patterns.

Thread Thread
 
perty profile image
Per Lundholm

As you asked, the GoF book was written before Java so no.