I've known some developers who were uncomfortable with abstraction in general, and like to have everything be as explicit as possible. So when reading code alo

I've known some developers who were uncomfortable with abstraction in general, and like to have everything be as explicit as possible. So when reading code along the lines of: var employee = employeeRepository.Get(12345); return employee.Name; they'll see the code as untrustworthy because without an explicit type name, you've got no idea what kind of thing 'employee' is. I suppose there's also the 'making excessive generics too easy' issue, though personally I'm not certain that excessive generics are necessarily so terrible. Oftentimes the alternative is to litter your codebase with a bunch of one-off classes that bloat the codebase without adding any value. I think I side with the camp that cites that practice as one of the things that used to really suck about working in Java.