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 the industry by opening a conversation between the two, providing
take aways, solutions to workflows, tools and discussions on everyday struggles.
This week Mustafa speaks to Sérgio Gomes, a Developer
Programs Engineer on the Google Developer Relations Team,
about the responsibility for design and why developers
don’t take that leap to become designers once and for all.
In this episode:
We ask who is responsible for design?
If our focus is the starting point or end point of what we do
[[["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\u003cem\u003eDesigner Vs Developer\u003c/em\u003e is a show exploring the intersection of design and development, offering solutions and discussions on industry challenges.\u003c/p\u003e\n"],["\u003cp\u003eThis episode features Sérgio Gomes and discusses the roles and responsibilities in design, particularly for developers.\u003c/p\u003e\n"],["\u003cp\u003eTopics covered include the ownership of design, the focus of the development process, and Material Design components and systems.\u003c/p\u003e\n"],["\u003cp\u003eThe episode is available as a video recording and audio podcast on platforms like Spotify, iTunes, and Google Music.\u003c/p\u003e\n"]]],["Mustafa interviews Sérgio Gomes, a Developer Programs Engineer at Google, on the \"Designer Vs Developer\" show. They discuss design responsibility, the starting versus end points of work, material design components for the web, and the overall material design system. The episode aims to bridge the gap between designers and developers by addressing industry challenges and providing solutions. Viewers can subscribe or watch the video recording of the podcast.\n"],null,["# Sérgio Gomes on who is responsible for design\n\nWelcome to *Designer Vs Developer*, a show that tries to solve the challenges\nfaced in the industry by opening a conversation between the two, providing\ntake aways, solutions to workflows, tools and discussions on everyday struggles.\n\nThis week Mustafa speaks to Sérgio Gomes, a Developer\nPrograms Engineer on the Google Developer Relations Team,\nabout the responsibility for design and why developers\ndon't take that leap to become designers once and for all.\n\nIn this episode:\n\n- We ask who is responsible for design?\n- If our focus is the starting point or end point of what we do\n- Material design components for web\n- Material design system\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/playlist?list=PLNYkxOF6rcIC60856GnLEV5GQXMxc9ByJ). \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)."]]
