The most common mistake is people conflating the type name with the instance name. I see them go wrong a lot, because if you would call it back and UI only, now I can use it for anything. It doesn't sort of hint at how you should use it. But thinking a more like an instance name could be a payment UI flow, but the type could be back and UI flow or something. That is a way, that's gonna solve, I think a lot of problems already people have. Because now you can reuse it, now the name is more clear. You know, kind of where it fits in the abstraction layer. And not gonna be feature specific, it

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode