❔ is Generic Repository a bad implementation of Repository Pattern?
Surfing the internet I have found several articles that say it is an anti-pattern because it is an abstraction of an abstraction. In a personal project I implemented the generic repository to avoid repeating code that is normally used in CRUD and if I need more specific functions I create a new interface and implement it. Should I remove the generic repository and create a specific repository for each database table even if I need repeat the code of a CRUD?
