THE OOPS! MOMENT
Wait a minute, how will we build all this?
🙋 Have the mockups ready. Then someone, with some knowledge of how code works, will slice it up into tickets.
💁 Design-person coordinates on making sure every ticket owner has what he/she/zhe needs. Hey, where do I get this font? Is this the latest icon set?
🙅 Someone finds we used a different button somewhere. We have a ticket. Which then needs to be taken up by someone.
🙆 And before we know it, we have huge piles of UX-debt.
I figured we need a component-driven UI design system in place. Design systems were the “it” thing in the market. And we needed someone to start building it to show it’s value.
Google summer of code
I was new to programming and there are tons of things you need to learn to get started, especially to get started to contributing to an open source community. My technical background and voracious reading habits on Medium helped me. As part of GSoC,
Collaboration and Team Work: Open source is all about effective communication. Being the only designer in the developer community, helped me learn skills to present my work, educate about design thinking and work with contradicting views.
Learned to Learn: Music metadata? Programming? Git rebase? There were and still are so many things I didn’t know. But I learned how to keep up, ask for help when needed and work hard to deliver!
Thinking about a product as a whole: I started out with a screen, but realized how we would need a system in place to scale across our projects over time. I helped came up with project roadmap and reach out to people with required skills to help out.
Some nice words by the community
I want all pages to be chhavi-fied. - Founder of the project, Robert Kaye
I really like what you did with the overview page. - An active editor
Thank you for your continuous work on this! I'm very happy that you addressed most of my concerns. - Community Manager
I like the new look, and the process you started is going somewhere, keep up the good job! - A loyal MusicBrainz fan