Archive | January 2014

Design Patterns

I’ll be exploring Design Patterns in depth with an upcoming series.  For now take a quick look at the practical application described below from Wikipedia page link (http://en.wikipedia.org/wiki/Software_design_pattern)

Design patterns can speed up the development process by providing tested, proven development paradigms.[6] Effective software design requires considering issues that may not become visible until later in the implementation. Reusing design patterns helps to prevent subtle issues that can cause major problems, and it also improves code readability for coders and architects who are familiar with the patterns.

In order to achieve flexibility, design patterns usually introduce additional levels of indirection, which in some cases may complicate the resulting designs and hurt application performance.

By definition, a pattern must be programmed anew into each application that uses it. Since some authors see this as a step backward from software reuse as provided by components, researchers have worked to turn patterns into components. Meyer and Arnout were able to provide full or partial componentization of two-thirds of the patterns they attempted.[7]

Software design techniques are difficult to apply to a broader range of problems. Design patterns provide general solutions, documented in a format that does not require specifics tied to a particular problem.

Advertisements

Change Agents

Ran across this today on USA Today about Robert Brunner designer of the Beats headphones.  http://www.usatoday.com/story/tech/2013/12/30/robert-brunner-ammunition-beats-change/3497185/

Great short on how important the design experience is.  Nice tribute piece. And totally relevant to Software Desgin though the article is clearly about industrial design of physically held products like the beats headphones.