I cannot give a yes or no answer in this case. "Generic" is too generic a term, to use it in this argument. It depends on the whole project and circumstances.

I cannot give a yes or no answer in this case. "Generic" is too generic a term, to use it in this argument. It depends on the whole project and circumstances. Usually I go with specifics and later refactor. The reason is simple: too often did I experience the case, that in order to change something in view, we had to alter the "generic layer". On the other hand, how can you build something generic, when you have not at least 2-3 use cases? "But we will never refactor" - I am one of the very few, who do just that. I worked my way up from dev to senior manager in order to give people the freedom I always missed.