The wages of sin: Over architecture in the real world

this time, this is a review of the sharp commerce application. again, i have stumbled upon the application by pure chance, and i have very little notion about who wrote it. the problem is that this system seems to be drastically more complicated than it should be.

i am going to focus  on different parts of the system in each of those posts. in this case, i want to focus on the very basis for the application data access:

are you kidding me? this is before you sit down to write a single line of code, mind you. just the abstract definitions for everything makes my head hurt.

it really hits you over the head when you get this trivial implementation:

public class emailtemplaterepository : repository<emailtemplate>, iemailtemplaterepository
{
    public emailtemplate get(emailtemplatelookup emailid)
    {
        return get((int)emailid);
    }
}

yes, this is the entire class.  i am sorry, but i really don’t see the point. the mental weight of all of this is literally crashing.