21–30 of 36 posts
Earlier quoted context omitted.
I think what's being said here is that it's easy to pick up the ideas of visual design, not the actual skill (I hope). As a budding designer, Dribbble is definitely helpful in allowing you to see "the bar" and improve how you approach certain projects. However, it is most definitely NOT easy to "pick up [visual design] by cruising Dribbble."
You are both referring to style.
I bet if I made a list like this highlighting what a programmer must have when working for a startup there'd be some serious hating going on. While this may be a good list if you want to read up for a month, this does not cover years of art theory, learning how to choose your battles, developing a refined sense of taste, pure objectivity, and a myriad of other skills that are subtly nuanced into almost every project.…
I hate this list. Want to be good? Look at sites/apps you admire and learn to emulate them. Don't read a 300 page book on User Experience or ugh, UX... unless you're doing for enjoyment.
Completely leaves out visual design. Maybe because polish is harder to encapsulate with a single book or because it's so easy to pick up by cruising Dribbble for inspiration, but it's still worth mentioning. Otherwise you get the average startup designer that's more of a developer in disguise.
I believe visuals are also a very subjective matter, and belong much more to the "talent" side of things, than to the "knowledge" one.
Earlier quoted context omitted.
The word "startup" has almost reached the status of buzzword. "Cloud based startup" would have been even better..
The use of "startup" along Amazon Associate links with very little value-add makes this page seem spammy.
When I could link the book's website, I did it.
Earlier quoted context omitted.
You are both referring to style.
Yeah, and?
The skills are critical for any front-end designer, not just the ones in startups. Companies that embrace skilled designers as their culture compete much better than others.
The word "startup" has almost reached the status of buzzword. "Cloud based startup" would have been even better..
While startups tend to look at results (the ones that survive), agencies tend to look at the customer, at least most of them.
I actually believe that most designers coming from an agency would be eaten alive in a startup, along with their "photoshop skills". This people don't even know what UX means, never conducted a usability test (usability = I look at the website and say what I think), and definitely don't read HN.
Earlier quoted context omitted.
The use of "startup" along Amazon Associate links with very little value-add makes this page seem spammy.
Hi, there are no Amazon Associate links: the only one Amazon Associate link I can think about is with Flanagan's book, and Mr. Flanagan is the associate, not me. I just thought removing it wouldn't have been polite. When I could link the book's website, I did it.
Earlier quoted context omitted.
Hi, there are no Amazon Associate links: the only one Amazon Associate link I can think about is with Flanagan's book, and Mr. Flanagan is the associate, not me. I just thought removing it wouldn't have been polite. When I could link the book's website, I did it.
My apologies, then. I probably moused-over the one link that did have the code.
Earlier quoted context omitted.
That has nothing to do with producing a good design, fast - which is the #1 qualification I'm looking for in a designer at a startup.
You really don't care if someone has a conceptual understanding of UI/UX? I guess that's fine if you're not doing anything unique. But if you are, how is your designer going to be able to think through the unique design problems posed by your product? I mean - take Mint, which has been widely praised for its design. Would a designer have been able to produce it by cobbling together half-understood components from oth…
I just don't think studying these concepts makes you better. Designing makes you better. Practice and good feedback. To me, UI and UX can read like buzzwords on a resume. I'm not saying they're not important components. I'm just disagreeing with how one should learn them. Perhaps I could have been more clear in my original comment.