title: Why use MVVM?
body: <p>Okay, I have been looking into MVVM pattern, and each time I have previously tried looking into it, I gave up for a number of reasons:</p>
  
  <ol>
  <li>Unnecessary Extra Long Winded Coding</li>
  <li>No apparent advantages for coders (no designers in my office. Currently only myself soon to be another coder)</li>
  <li>Not a lot of resources/documentation of good practices! (Or at least hard to find)</li>
  <li>Cannot think of a single scenario where this is advantageous.</li>
  </ol>
  
  <p>I'm about to give up on it yet again, and thought I'd ask to see if someone answer the reasons above.</p>
  
  <p>I honestly can't see an advantage of using this for a single/partner coding. Even in complex projects with 10's of windows. To me the DataSet is a good enough view and binding like in the answer by <a href="https://stackoverflow.com/users/235666/brent">Brent</a> following <a href="https://stackoverflow.com/questions/2652166/best-method-for-binding-combobox/2652700#2652700">question</a></p>
  
  <p>Could someone show an example of where using MVVM pattern would of saved time when compared to XAML DataBinding.</p>
  
  <p>100% of my binding is done in XAML at the moment. And therefore I don't see the point of the VM as its just extra code behind that I need to write and depend on.</p>
  
  <p><strong>EDIT:</strong><br>
  After spending the afternoon researching about MVVM I have finally found something that made me realise the true benefits of it from this <a href="https://stackoverflow.com/questions/1644453/why-mvvm-and-what-are-its-core-benefits/1644955#1644955">answer</a>.</p>