Be nice. Or else.
San Francisco Product Design Instructor at Tradecraft (jakeflem.com) Joined over 4 years ago via an invitation from Allan G.
Yep, totally. Like I said, I'm sure most people writing articles like this are trying to help people learn about these tools, but in certain instances they might also be leading people down the wrong path.
The headline is a bit "tongue-in-cheek". I mention what you brought up within in the article. That's why I was confused. Glad we agree.
Dropbox usually does the trick. Sometimes will pair that with git.
Recently been using Abstract. It's pretty great.
This is rad. Giant face is a bit creepy, but love the concept.
This made me lol with coffee in my mouth. Thank you.
Nice, Tom! It definitely can be daunting just starting out as a designer with the amount of tools, methods and opinions. But I think that's actually a good thing. I do believe it's on the designer to form their own opinions about tools. I just think we can do a better job at writing useful articles to help people form those opinions.
Not sure what is contrary about that. Hearing both negatives and positives about a tool is a good thing.
I don't think just because a tool is established that it can't be phased out or rendered obsolete in favor of another. We see that all of the time. My argument is more around the misuse of those tools and blanket advice based on that misuse.
Man, don't ruin my muffins!
Here's an analogy:
Say, I'm looking for a book. You work in a library right? You can help me. I'm counting on you. I don't know much about libraries other than they've got books, computers, late fees. Stuff like that. I just know I want a book to read that helps me learn how to make a kite. Here's your advice to me:
"One book you should definitely not read is 'Making Kites'. I read that book, made up my own design and didn't check it with the book's design and my kite didn't fly! It was stupid! I talked to this other guy that did the same thing. You should never read that book."
A person who has also read that book and over hears our conversation might say:
"Wow, that is really bad advice. It doesn't even seem like you read that book. I read that book, followed the directions and my kite flies great. You should really learn how to follow the directions in that book before you give advice to people on whether or not they should read it."
If you still aren't getting my argument, please read on.
I brought up well-known designers and companies, because they have a larger influence in the design community. That's just a fact. Newer designers read these articles that are saying this or that tool sucks, because I sucked at using it and say to themselves, "Oh I guess that tool sucks." They might go on with their day/foreseeable future never considering that tool again until they encounter its proper use in the wild or are asked about their opinion on that tool in an interview. Often times that leaves them looking like a dummy, especially if they give the opinion and reasoning from some of these articles. So yeah, it's damaging. Really. Absolutely. 100%.
I work with new designers every single day who are looking to seasoned designers for guidance. A lot of the time, that guidance is found in a blog article. There are so many articles, enough to prompt me to start this discussion, that advocate to not use personas (or another tool/method) because the person trying to use them just made something up and then made a bunch of decisions without validating those assumptions throughout the process. I'd really love to hear your thoughts on how this is good advice.
Tools have flaws. All of them. I'm not arguing to not write articles about the flaws of design tools. I'm arguing to not give shitty advice.
It really is an amazing time to be a designer. I'm glad so many people are writing about design and I truly believe all of the articles I come across are written to be helpful. However, I think some of them fail at being helpful to their readers.
Totally drove that point all the way home, Dirk!