Comments on: Do Not Use Design Patterns Upfront

By: npoet.ru

npoet.ru — Sun, 09 Aug 2009 11:27:07 +0000

good info keep it coming

By: Patterns as an afterthought «

Patterns as an afterthought « — Fri, 31 Jul 2009 17:32:41 +0000

[...] UncategorizedTags: Development, patterns Jovan Stanojlovic presents his case () against blindly adopting Design Patterns. I often see new or simply inexperienced game programmers trying to brute patterns into their code [...]

By: Twitted by alex_klimov

Twitted by alex_klimov — Fri, 31 Jul 2009 07:03:27 +0000

[...] This post was Twitted by alex_klimov [...]

By: mitja

mitja — Thu, 30 Jul 2009 13:25:06 +0000

Well let’s look on the bright side — if the novice indeed doesn’t know better than applying patterns to everything from toast to C, then, if he or she indeed has potential to become good programmer, should eventually get experienced enough to realize the mistake.

I think what we should really be worried about is something @ronald mentioned above, and that is spreading the idea of thinking in patterns as a panacea of sorts.

“I see you struggling with that code. Are you tired of struggling with what seem like easy to approach patterns. Hi, I’m Dmitry, and I’m here to tell you about patterns…”

By: Twitted by julianodc

Twitted by julianodc — Thu, 30 Jul 2009 12:51:07 +0000

[...] This post was Twitted by julianodc [...]

By: links for 2009-07-30 « pabloidz

links for 2009-07-30 « pabloidz — Thu, 30 Jul 2009 12:04:48 +0000

[...] Do Not Use Design Patterns Upfront Blissful Designer – Blog of Jovan Stanojlovic (tags: programming anti-patterns) [...]

By: Chandima Cumaranatunge

Chandima Cumaranatunge — Thu, 30 Jul 2009 08:04:06 +0000

I agree that it is easier to see where patterns can be applied when code already exists. I also agree that novice programmers get gung-ho on design patterns and try to force application design into patterns.

However, I don’t think thinking in patterns initially is trying to “apply a pattern to a non-existent problem” simple because the problem/scenario already exists. Software engineering is problem solving and experienced developers can see/visualize the problem space in terms of patterns.

A good example of architecting an application framework using patterns is described by Kent Beck and Eric Gamma when they developed JUnit

http://junit.sourceforge.net/doc/cookstour/cookstour.htm

By: What I’d Tell Myself About Design If I Were Just Beginning | cwash into software

Thu, 30 Jul 2009 02:25:42 +0000

[...] books (especially right after we’ve finished them) and, as the first order of business, go to town solving problems we don’t [...]

By: John Doe

John Doe — Wed, 29 Jul 2009 19:34:12 +0000

…that being said it’s now not necessarily *bad* practice and hence the comment on patterns being “good practice” could very well be true in certain contexts/environments. With the use of standard patterns there is an implicit documentation, structure and understanding of that piece of code built into it, and can be VERY useful for people unfamiliar with it trying to understand it. IMO they’re still tools in the toolbox–no more, no less.

By: Jovan

Jovan — Wed, 29 Jul 2009 18:53:00 +0000

I am glad you enjoyed reading the article, and can’t say I am surprised with the response. Unfortunately it will be hard to abolish such thinking until such developers -start- thinking .