Creating a Collaborative Environment -- Designer vs. Developer #1
ฝัง
- เผยแพร่เมื่อ 14 มี.ค. 2017
- In this episode Mustafa Kurtuldu speaks to Jake Archibald about communication and the assumption that designers and developers sole role is to either make things look pretty or to be a cog in a machine with no soul.
Welcome to Designer vs. Developer, a show that tries to solve the challenges faced in industry by opening a conversation between the two, providing take aways, solutions to workflows, tools & discussions on everyday struggles.
You can listen to an extended version of our conversation in this podcast: goo.gl/wMKu70
Read our blog post here: goo.gl/Y8fgrt
Learn more about the subjects mentioned in this video:
Basics of UX: goo.gl/at8VLW
Design Sprints: goo.gl/XBon9Q
Performance: goo.gl/08igDR
Subscribe to the Chrome Developers Channel: goo.gl/LLLNvf
Watch the rest of the series: goo.gl/eIk8r6 - วิทยาศาสตร์และเทคโนโลยี
.video-overlay{ background-color: rgba(0,0,0,1); }
All of this is based upon the assumptions, that people take their ego back and prioritize the need of the product/the user they create it for. Issues discussed here are not inherent to the professions, its because people don't communicate well or because they hire rockstar designers / developers, only there to raise their ego by being treated like a knight in golden armor. The key to all of this is not to hire people who only design or develop for attention, but instead to create actual value. Just my two cents.
Absolutely great video with solid advice, guys. Our dev team has experienced some disconnects with the design team, so this is spot-on and will definitely be helpful. Keep 'em coming!
Mario Parra glad you like it, stay tuned for the next episode :)
Very cool initiative Google! Very promising!
Good one and much-needed video series. We're in it together, but sometimes it feels like we're on opposite sides.
Glad you like! Things work best when we talk more I find.
@ Mustafa,
Very good podcast idea, congratulations.
I do wish, however, that, at least in the descriptions if not the introductions, you described the actual roles in slightly more depth (i.e., is Jake front-end or back-end?; are you a digital or graphic designer?) in order to give the interviews more context.
Thanks.
Thanks for the tip, I think ill add that to the description to give more clarity! :)
Great idea for the show! Want to see more
Thank you my friend :)
Love this
I've done a bit of freelance at #Google (maybe before these guys were born - lol) - and I was shocked at how UNSOPHISTICATED Google was/is in the #Design process. These, errm, rows bxn #designer/#engineer (to use an old Ford motor company juxtaposition) are age old. Form follows function is the surviving constant in this equation. There will ALWAYS be THREE types working in this sphere: the #DESIGN only type. The #Engineer only type - and the #HYBRID type - who can easily work w both "sides of the brain" if you like.
I saw a talk by Jake on I/O round about 5 weeks ago and no I see him everywhere :o
Marius Niveri I haunt the web
You sure, you havnt overtook it yet? I mean you made the god damn service worker. Which by the way should be called "I-make-the-web-great-again-worker", or something like that ;)
I wonder what it would be like to only work by assembling tried-and-true building blocks, and having a team painstakingly experiment to create new building blocks, one at a time... and stay away from mixing the 2 activities.
What about someone who wants to be both? I study Computer Science but I really want to be a UX designer and developer. Is there a place for that sort of a person or would you rather recommend sticking to one side of the process?
Bilal Kazi i do both, i say do everything you can :) sky's the limit
Bilal Kazi in a lot of places both is a requirement. Smaller businesses can't employ fulltime designers and developers, and while they may use consultation or external designers for big chunks a lot of the design is done by the developer.
It helps to become aware of your own learning and working styles. Some folk do better by specializing, others by knowing as much as possible about everything. I do advise people more big picture and pattern oriented (myself) to also at least do one thing well. Mustafa nails it though: "do everything you can".
You can do both! I personally don't like designing. So, I just stick with development.
That’s beautiful!
why video is so dark ?
Nice!
Hi Mustafa!!!!
HI!
+1 Lets not treat software product development like a conveyor belt. I much prefer to be included in more aspects of the product than just my specialty.
Absolutely! I have found some of the best insight into design has come from other places.
Hi Mustafa from here from Paris
HELLLOOOO
How things are in your designs?
The missing person in that conversation is: client/product owner/boss/marketing executive
Absolutely, I guess what we are trying to say is 'be more inclusive rather than defensive', which sounds obvious I know but sometimes can be hard to do.
I don't know, I builded two wordpress sites recently and keeping up with updates plus the added work of apply new designs is quite overwhelming.
If design changes didn't replace past work, that would be awesome, but I guess that's how this bussines is.
Change is something that we have embrace. Somethings things are never done - done. Its part of working on living products I guess :)
collaboration, yes. however, it is all design.
Blend multiply again no!!!!!