I agree with you and isn't it a code smell in itself to put interfaces next to their implementations? In the CleanArchitecture example there are only implementations in the Infrastructure project. The interfaces life inside the Core and UseCases projects.
Distraction-free reading. No ads.
Organize your knowledge with lists and highlights.
Tell your story. Find your audience.
Read member-only stories
Support writers you read most
Earn money for your writing
Listen to audio narrations
Read offline with the Medium app
I am a software developer from germany. Blogging about programming and tech related topics. I ❤️ open source and privacy.
Ok. But I don’t think this separation of interfaces and implementations is clear to all readers of your article. For for example an Infrastructure layer, I would prefer to have a Infrastructure. Interfaces and an Infrastructure.Implementations assembly
--
