Bookmark and Share

Software modelling and design - designers should code, and vice-versa

Image representing 37signals as depicted in Cr...

Image via CrunchBase

Listening to the latest 37signal podcast episode, I reflected on the artificial separation (often to the point of hermetical confinment) between interface design and code in the software creation process.
At 37signals, Ryan Singer encourages designers to know enough about Ruby on Rails to change the interface themselves instead of relying on programmers.

Image of Ryan Singer from Twitter

Image of Ryan Singer

It's completely key that the designers are working in source code. I can't conceive any other way of working, because with applications the cost of having somebody translate all of  the designs is too high. [...]
It means that you can't change things. It's really adding too much friction and weight in the feedback cycle.

 

Creative Commons License
Except when explicitely indicated otherwise, Duboc.me by Jean-Rémy Duboc is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.0 UK: England & Wales License.
Permissions beyond the scope of this license may be available at jr.duboc@gmail.com.