“Interface vs. implementation” is a split that runs all the way down a software project, from UI vs. code to the names of individual methods. Knowing which of the two hats you’re wearing at a given moment is key to keeping complexity under control and communicating better with your team.
About Ryan
Ryan joined 37signals as a UI designer in 2003. He worked closely on the design and concept of Basecamp, Backpack, Highrise, and Campfire. Also a programmer and strategist, Ryan's role includes managing product development and guiding decisions at the company.Read all of Ryan’s posts, and follow Ryan on Twitter.
Realized by Ryan on August 19 2009. There are 2 comments.
Pete 19 Aug 09
I like these bite-sized realizations but they can be a bit Jack Handy. This particular one is really interesting and I hope Ryan elaborates further in a full-length post.
Mike Riley 19 Aug 09
I think this goes hand in hand with “don’t have meetings”. I’ve been sitting through a lot lately and have noticed that it’s impossible to hammer down which of the two sides you’re talking about with so many people simultaneously trying to give feedback.
This discussion is closed.