Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Recently I worked on a fairly large project involving C# and MVVM. This application had around 160 projects in the solutions each seprarated into their own layers. As I have been working on this application for almost a year, building it from scratch as part of a team, I am now coming off that project and onto smaller more trivial projects.

As I was beginning to develop a small in-house tool I found myself trying to mimic the larger applications structure and layering but in the end I just had a simple application with several DLLs which I know I wouldn't have done if I had not worked on that larger application before.

I am just wondering if there are any techniques I can utilise to stop myself from turning a "code-behind" style trivial application into a full blown MVVM application?

Or should I continue developing as I am and try to keep the unnecessary fluff out of the project?

share|improve this question

1 Answer 1

up vote 2 down vote accepted

I am just wondering if there are any techniques I can utilise to stop myself from turning a "code-behind" style trivial application into a full blown MVVM application?

Yes you can easily stop yourself from over-engineering the application. Always look for the simple solutions over complex, and remember KISS and YAGNI principles.

share|improve this answer
1  
I think YAGNI really applies to what I am doing. I am trying to imagine the different scenarios this piece of software will be needing to be adapted to and thus creating a overly complex app. Thanks. –  stuartmclark Sep 16 '12 at 15:41

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.