Be nice. Or else.
Designer on the Product Team at Apartment Therapy Joined almost 5 years ago
I work in a media company with 3 key "users," Stakeholders, partners and users. Stakeholders are our content-creators and editors, partners are our advertising clients and users are our actual end-users. Our entire product team is fighting the same things described in your piece daily. Appreciate your broaching this subject. Keeps me beating my dead horse.
Watching The Exorcist tv show. I just wrapped a 9-month side project so I'm taking a break.
I think his argument is structured in a painfully obtuse way but there are 2 parts that I break down (this is just my opinion, I'm in no way an expert on this type of thinking) as pieces of what he's maybe trying to get at? Maybe?:
Organizations that silo design away from the input of other members of the org are doing it wrong. This happens. It's bad. It's often attributed to the hubris of the designers being bummed that a PM is trying to tell him what would "look best." I think we've probably all been there early in our careers.
We're too precious about titles, but there's a psychology to that. When you strip away the specific title of "Designer" from someone using that to their financial and career advantage you're damaging something they are attached to and that directly influences their lives. That can elicit a very strong reaction. This is true of what a "designer" even is as well. When everyone in our org is a designer we've democratized (what should be seen as) a trade and as a result, there's less value in it and that's fucking scary.
In the long term theres this thing competing that I'm curious about. We, as designers, have always wanted design to be democratized and spread so that more things are well-designed but the more that happens and the more people we give seats at the design (kiddie) table, the more this is going to happen and the more these questions will be raised (hopefully in a more coherent manner).
I dunno. I think his intentions are good, just kind of executed in a less than ideal way.
I had no idea Qs was still in dev. gonna try it again
I mean guys like Justin Mezzell and Rogie are great. Kyle Lambert over at OLark is a great guy. In addition to twitter, just get to know people. Go to a meetup or to a conference. Those people will have information and views you wont. Expands the brain muscle.
Ultimately design is about people. If you're not an asshole, you're striving to do work that is good for users and you're engaged in the design community at large (twitter, seriously) you'll grow in your carer. That's not sexy or groundbreaking like "Hey man, learn React!" or "Copy people until you get better." it's a little more practical but it's 100% true across most anyone I know who's successful in this industry.
I think the ES6 part is related to the React specific path he's supporting here.
Uh, yes please I work on 2 editorial products and this is insanely helpful. I ask for stuff like this in the slack channels I'm in constantly and I feel like I never get any response
Super excited to try it out thanks for the information and good luck through the beta and release! You will likely see my name in the pre order group in the coming weeks!
I think this looks really interesting as a designer who works on a product team that users React.
Are you at all concerned (as a team) about the quality of code output? Up to this point we haven't seen (m)any design tools with the ability to output fully usable code out of the box. What makes React Studio different?
Just as a curiosity - Does it use built in React state switching tools or something like Flux/Redux built in to handle that?
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.