Re:How I Designed Code Year in 1 Hour
by sgdesign on Tuesday January 03, 2012 @12:42PM
(#3420470)
As a designer, this is why I love working with startups. You can go from idea to actual live site in a few days only.
Paradoxically, it was a lot of fun working on such a short timeline: it basically took all the pressure off and made sure I couldn't second-guess myself.
Re:How I Designed Code Year in 1 Hour
by culturestate on Tuesday January 03, 2012 @02:25PM
(#3420919)
"Paradoxically, it was a lot of fun working on such a short timeline: it basically took all the pressure off and made sure I couldn't second-guess myself."
I couldn't agree more. I often give myself artificially short deadlines if I'm having designer's block, it works wonders.
Re:How I Designed Code Year in 1 Hour
by pdenya on Tuesday January 03, 2012 @01:28PM
(#3420683)
That's part of what appealed to me at the ad agency I worked at. It's fun to build things as quickly as possible sometimes. I'm glad I'm not doing that constantly anymore though.
Re:How I Designed Code Year in 1 Hour
by phil on Tuesday January 03, 2012 @04:08PM
(#3421305)
Great writeup, and helpful for people like me. I often know exactly what message I want to deliver and the visual hierarchy I want, but coming up with a nice layout is harder. So the break down is good to see.
It was pretty shocking to see the McCurry Afghan girl photo as an icon placeholder though. That's probably one of the top 5 news photos of all time, and I'm not alone in having a strong emotional reaction to it?
Re:How I Designed Code Year in 1 Hour
by RoboTeddy on Tuesday January 03, 2012 @02:03PM
(#3420827)
It's interesting to see the iterative thought process of a designer as they go through and make changes. I wonder if it'd be a good way to learn design. How about Design Year? :P
Re:How I Designed Code Year in 1 Hour
by sgdesign on Tuesday January 03, 2012 @12:50PM
(#3420506)
Aren't we actually agreeing? My point was exactly that good design does not depend on the timeframe. It can be quick, or it can be slow. So you shouldn't be afraid of going fast sometimes.
Re:How I Designed Code Year in 1 Hour
by ed209 on Tuesday January 03, 2012 @02:40PM
(#3420986)
I agree that time spent does not equal good design. But years of experience is always required before doing good design in a short time.
Always a good read :)
"...you were asking me to design a logotype which would have taken me a few hours and fifteen years experience..."
from http://www.27bslash6.com/p2p.html
Re:How I Designed Code Year in 1 Hour
by enra on Wednesday January 04, 2012 @04:53AM
(#3423475)
It depends of the design, but I think generally it takes me longer to design mockups than to implement them.
When implementing you know what you should do, and when know your tools, you can pretty much do it as fast as you can type.
When designing you start from scratch. You try to wrestle all the ideas and requirements with the best practices and the right style, to create something that's new and works.
So I think designing well is much harder than implementing the design well.
Paradoxically, it was a lot of fun working on such a short timeline: it basically took all the pressure off and made sure I couldn't second-guess myself.
I couldn't agree more. I often give myself artificially short deadlines if I'm having designer's block, it works wonders.
It was pretty shocking to see the McCurry Afghan girl photo as an icon placeholder though. That's probably one of the top 5 news photos of all time, and I'm not alone in having a strong emotional reaction to it?
Maybe Cookie Monster as a placeholder instead? http://www.google.com/search?q=cookie+monster&hl=en&...
...Then it will have been a decent year
http://sachagreif.com/the-design-freebies-list/
http://codecademy.com/jobs or jobs(at)codecademy(dot)com
thanks!
For example, one week you'd design a sign-up form, the next focus on contrast, etc.
Always a good read :) "...you were asking me to design a logotype which would have taken me a few hours and fifteen years experience..." from http://www.27bslash6.com/p2p.html
When implementing you know what you should do, and when know your tools, you can pretty much do it as fast as you can type.
When designing you start from scratch. You try to wrestle all the ideas and requirements with the best practices and the right style, to create something that's new and works.
So I think designing well is much harder than implementing the design well.