Surma on existing design tools being fit for purpose
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 Surma, a Developer Advocate on the Google
Developer Relations Team, about whether the design tools we use are fit for
purpose and how Dash Elements (now renamed to ‘
HowTo: Components’) will help educate designers and developers about
important topics like accessibility.
[[["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 that fosters conversation between designers and developers to address industry challenges, offering solutions, workflows, and tool discussions.\u003c/p\u003e\n"],["\u003cp\u003eThis episode features Surma, a Google Developer Advocate, discussing the adequacy of current design tools and the role of HowTo: Components in educating designers and developers on accessibility.\u003c/p\u003e\n"],["\u003cp\u003eKey topics explored include design tools, designers' understanding of code, HowTo: Components (formerly Dash Elements), and web best practices and patterns.\u003c/p\u003e\n"]]],["Mustafa and Surma discuss the suitability of current design tools and how to bridge the gap between designers and developers. They explore how designers can learn code and introduce '[HowTo: Components]' (formerly Dash Elements), which aims to educate both roles on web best practices, patterns, and accessibility. The episode tackles industry challenges, workflow solutions, and tools. The podcast, \"Designer Vs Developer\" aims to open conversations and address these common struggles.\n"],null,["# Surma on existing design tools being fit for purpose\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 Surma, a Developer Advocate on the Google\nDeveloper Relations Team, about whether the design tools we use are fit for\npurpose and how Dash Elements (now renamed to '\n[HowTo: Components](https://github.com/GoogleChrome/howto-components)') will help educate designers and developers about\nimportant topics like accessibility.\n\nIn this episode:\n\n- The design tools we use.\n- Designers learning about code.\n- Dash Elements (now renamed to '[HowTo: Components](https://github.com/GoogleChrome/howto-components)')\n- Exploring the best practice and patterns of the web.\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)."]]
