AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
5min chapter
Domain-driven design with Go (Go Time #273)
Changelog Master Feed
The Importance of Loyalty Handlers
I tend to have, my handlers kind of chunked up based on what they're related to. So I think I would tend to do something along the lines of loyalty. And loyalty I might have a handler.go with all the loyalty related handlers inside of payments. There'd be another set of payment handlers. But it's also hard sometimes where you'll be setting up your application and it really needs three different sets of handlers to even function correctly. It feels a little bit weird there where you're like, well I need all three of these anyway. Why are they separated? They're not as linked as they are.
00:00
Transcript
Episode notes
Get the Snipd
podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered
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