Technorati Tags: C#,Architecture,Standards These days I’m working a lot more on not just code features, but also more architecture from scratch. That is, creating many new Abstract classes, Non-Abstract classes, Interfaces and utilizing more and more Design Patterns. Thus every field, member, property, etc. created in the class or interface heirarchy tree becomes very important in how you define them and where you define them as well as any dependencies that they may be carrying. You try to create a class or interface structure with as least # dependencies as possible, so that a change to one object will...
I hear a LOT of developers refer to what are essentially N-Layers as “N-Tiers”. This kind of bugs me a little when I see or hear it from developers.
First of all, they are not even close the same thing, and it’s important as a developer to get this straight so that you are using the terminology properly. The difference is simple but very important when you’re talking about your applications. They should not be loose terms and intermingled as about probably 90% of the developers out there