Linked by Thom Holwerda on Wed 11th Jul 2012 01:24 UTC
Permalink for comment 526331
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2007-02-18
I personally think programs should be written to be as skinnable as possible so that designers and programmers don't have to work together at all. The programmers provide the functionality and infrastructure as modular (signal driven) as possible.* Designers just design the interface and glues everything together with signals however they like.
But actually my comment was meant to be taken as - if designers really want to get noticed above the noise of many designers coming onto the scene, they really should know enough programming to produce working prototypes of interfaces.
As others have noted, the website is all about flash which creates an impression but overshadows any suspicion that it had any interesting ideas. It ends up only showcasing the designer's aesthetics in website design and not the actual concept he was selling.
* I work on Eclipse plug-ins. It fails really hard - its design patterns end up completely going against the principles of "information hiding" into full blown coupling.