AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
2min chapter
Avoiding bloat
Go Time: Golang, Software Engineering
Is There a Need to Reveaw Dependencies?
I do consider, like, every dependency as your own responsibility to maintain and to fix things when things go critically wrong. With that rule in place, you've certainly been sensivized quite strongly not to include many dependencies. I think there is a case where you don't need to reveaw them. If you're actually paying someone else to maintain that cold base, like, then you're intentionally offsetting yur own responsibility to somebody else. But i think it has many, like benefits if you do reveal them, even if you don't understand them, right? Because if you're revieaing oter coat, you might look at e how they built things. Maybe you
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