By bloid
via codebetter.com
Published: Oct 01 2008 / 08:19
Sorry guys, but it's time to rant. I see so many people needlessly complicating their architecture and deployment by insisting on using separate assemblies for every layer of the app or even doing the trick where interfaces are in one assembly and the concrete classes are in another assembly. Stop it! It's a waste of time. Logical de-coupling from UI to business logic to infrastructure to the database is very important, but using separate assemblies doesn't do anything to guarantee that decoupling. You can separate your assemblies all you want, but making the UI depend on the implementation details of the business code in the other assembly is still harmful tight coupling
Add your comment
