Jake Archibald on creating a collaborative environment
Stay organized with collections
Save and categorize content based on your preferences.
Welcome to Designer Vs Developer, a show that tries to solve the challenges
faced in industry by having an open conversation between the two, providing
take aways, solutions to workflows, tools & discussions on everyday struggles.
This week we speak 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["\u003cp\u003e"Designer Vs Developer" is a show that fosters open conversations between designers and developers to address industry challenges and improve workflows.\u003c/p\u003e\n"],["\u003cp\u003eThis episode features Jake Archibald and explores the roles and perceptions of designers and developers, challenging the idea of limited creative input.\u003c/p\u003e\n"],["\u003cp\u003eTopics covered include the impact of open workspaces on design, the effectiveness of design sprints, Jake's work on service workers, and the need for better version control practices among designers.\u003c/p\u003e\n"],["\u003cp\u003eThe episode is available as a video recording on YouTube and as an audio podcast on Spotify, Feedburner, iTunes, and Google Music.\u003c/p\u003e\n"]]],["The episode features Jake Archibald discussing communication between designers and developers. Key topics include defining roles, open-space design, design sprints, and service workers. They address the common misconception of designers focusing solely on aesthetics and developers as mere cogs. The conversation also touches on designers' lack of version control. This show aims to bridge the gap between designers and developers, offering solutions to workflow challenges.\n"],null,["Welcome to Designer Vs Developer, a show that tries to solve the challenges\nfaced in industry by having an open conversation between the two, providing\ntake aways, solutions to workflows, tools \\& discussions on everyday struggles.\n\nThis week we speak to Jake Archibald about communication and the assumption\nthat designers and developers sole role is to either make things look pretty\nor to be a cog in a machine with no soul.\n\nIn this episode:\n\n- Roles and place in design and development\n- Designing in an open space\n- Design sprints\n- Jake's service workers\n- Designers lack of version control\n\nSubscribe to Designer Vs Developer Podcast via\n[Spotify](https://bit.ly/MustafaOnSpotify)\n[Feedburner](https://goo.gl/USHXv8),\n[iTunes](https://goo.gl/1E9U0G) Or\n[Google Music](https://goo.gl/qCBlST)\n\nWatch [the video recording](https://www.youtube.com/watch?v=8T94qu8IWWk). \nWas this page helpful? \nYes \nWhat was the best thing about this page? \nIt helped me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had the information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had accurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was easy to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nNo \nWhat was the worst thing about this page? \nIt didn't help me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was missing information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had inaccurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was hard to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new)."]]
