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
Play full episode
Remember Everything You Learn from Podcasts
Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.
