Tag Archives: Architecture

Waterfallish isn’t [always] foolish!

Your first goal is an MVP – minimum viable product [not Microsoft’s most valuable professional.] You define a few features and envision a few screens. Sure, without going into any details. And you go with scrum from the beginning. You’re … Continue reading

Posted in Development | Tagged , , , , | Leave a comment

Creating great products requires outstanding functional design

(I’ve recently twitted two examples, but I think it the idea deserves a more general blog post, so here we go.) It’s not enough to be an outstanding developer to be able to create great software (that sells). You need to also … Continue reading

Posted in Development | Tagged , , , , , | Leave a comment

On onion (cone?) architecture

“High level modules should not depend on low level modules. Both should depend on abstractions.” The first three circles starting with the central Domain define the application core. Each of these is a collection of high level modules. The outer-most … Continue reading

Posted in Architecture | Tagged , , | 3 Comments

Stop over-abstracting

Developers are very good when it comes to abstracting things, be this: 1) generating base or generic classes to inherit from or reuse; 2) generic or overloaded functions called with arguments instead of standalone ones; or 3) reusing code under multiple technologies even if it’s … Continue reading

Posted in Architecture | Tagged , , , , , , | 3 Comments

Unit of work over Entity Framework

Many unit of work and repository implementations over Entity Framework do not respect the interfaces of the patterns correctly, and therefore the abstractions do not serve any purpose. In my opinion, the single reason for (and goal of) abstracting unit of work and … Continue reading

Posted in .NET | Tagged , , , , | 5 Comments