So Dev

Messy ViewModel

In good old days, it's the code behind that has everything dumped into it and causing the corresponding application hard to maintain.  Now in the MVVM world, it's the ViewModel that can become a dumpster.  It takes some serious effort to manage it so that the application code can stay maintainable.  Small things like organize the code in tidy way, use good naming, group code using "#region", put in decent remake ... all these can make a huge difference on the maintainability and eventually scalability of your code.

The rule of thumb of ViewModel is that if the code is bigger than couple hundreds of lines, something is seriously wrong.

posted by Deecay @ 11:32 PM