Почему интерфейсы лучше размещать в месте использования - GoLang best practices

Why it's important to describe interfaces not next to the implementation, but where they're used. ---- ❤️ If you'd like to support the channel's development: Secret Telegram channel: Ruble donations: https://t.me/+1UPXV_DGnG1mODJi Euro donations: https://t.me/+hedI8LevYTc5MDM6 https://boosty.to/nikolay.tuzov   / tuzov   Other projects: 👾 My Telegram channel: https://t.me/ntuzov 🗣 Telegram chat: https://t.me/+zsSZ63wEJDs3NGVi 👀 GoLang Digest: https://t.me/golang_digest - my regular collections of interesting materials about Go. ---- Timecodes 00:00 Introduction 00:32 Minimalistic Interfaces 00:43 Implementation Independence 00:57 Web Service Example 01:30 What's wrong with this service? 02:42 How to fix it? Interfaces based on where they're used! 04:52 Decreased system cohesion 05:39 Improved code clarity 07:02 Increased system flexibility 08:03 Testing and Mocks 09:06 Disadvantages of the Approach 11:58 Duck Typing - What is it? 13:52 Conclusion #golang #ntuzov