If you've been in the game long enough, you get informed by upper management of a grand promise due in just a little over a month. Something like rewriting an entire suite of applications in a new technology in 6 weeks. That's what I'm facing at the moment. The promise has been made, so after you pick your jaw up off the floor, what can you do? Do What You Can The number one thing that causes your gut to tie itself in knots is all the stuff you know you don't know. The unknown things linger in your mind like a cancer undermining anything possible. Norman Vincent Peale is credited with the quote "Shoot for the moon. Even if you miss, you'll land among the stars." Aside from the bad astrophysics, that sentiment is what you need to start with. Be aware of the deadline, but don't let it consume you. It's too easy to spend a lot of energy fretting over it that is better spent on just getting stuff done. Get the Griping Out of the Way It&
I'll be honest, there's a lot of MVVM frameworks out there, all promising to be the bees knees, light weight, etc. One of the common threads between all of them is the insistence on using their brand of dependency injection to do the job. There's good reasons to use dependency injection when you have a big enough project, and there's also a lot of good reasons not to use dependency injection for small utility projects. MVVM In a Nutshell Model-View-View Model isn't a new pattern, and there's a couple flavors out there. The basic pattern works like this: Model -- the representation of application data with bind-able properties. ViewModel -- a layer with a bind-able Model property that handles view specific logic View -- the user control or window that is shown to the user that binds directly to the ViewModel and Model. The two flavors are "View First" and "Model First". View First MVVM has the view layer reference other view lay