5

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?

Improve this question
1
  • its like listening to myself! Commented Aug 23, 2016 at 10:45

1 Answer 1

Reset to default
3

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.

Improve this answer
1
  • 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. Commented Sep 16, 2012 at 15:41

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.