I've never had this kind of issue with generics although I also avoid using a repository pattern as much as possible. I prefer to let the database engine do database things, like storing and querying data, and the code do code things, like calculating and such.
A lot of what you're describing seems to go back to the YAGNI principle. We can get caught up in creating an elegant set of interfaces and classes and forget what the objective of the code is supposed to be.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've never had this kind of issue with generics although I also avoid using a repository pattern as much as possible. I prefer to let the database engine do database things, like storing and querying data, and the code do code things, like calculating and such.
A lot of what you're describing seems to go back to the YAGNI principle. We can get caught up in creating an elegant set of interfaces and classes and forget what the objective of the code is supposed to be.