DarksideCookie

I think it is time for another rant. Actually I really don’t, as my blog is supposed to be about coding, not about me ranting… It seems like my blog has slowly gone from code centric posts, to ramblings of a grumpy Microsoft developer. Sorry about that, and I promise to focus more on code in the future…

Lately I have travelled around and talked at a bunch of conferences, and heard a lot of really smart people talk about a lot of really cool things. This got me thinking a bit about my own way of dealing with new technology, as well as about my own way of doing things today… The result of this thinking is that I am going to try and make 2 changes. First, I am going to try and get out and about and try more new stuff. More frameworks, technologies and maybe even more languages… Hopefully this will fuel my blog with more code related posts as well as interesting revelations and thoughts. Secondly, I might have revisit my stance on unit testing and TDD…

More...

Ok, so MVVM is obviously about Unit testing right? Well, I don’t really agree, but it is definitely a part of why you chose MVVM, even if it is only a small part of the reason for me. I have been using the MVVM pattern for a while now, but I still haven’t started unit testing my code properly. I know I should, but for different reasons I never get around to it. Mostly due to time constraints.

And for all of you that tell me that writing unit tests will not take more time as there will be less bugs to fix, bug off! It does take time. It does include mocking or stubbing services. It does take time to figure out how to write useful tests. And first and foremost, it takes time to get the experience needed to do it fast… So argument ignored!

What I do do though though, is keeping it in my mind when I design my VMs. I always consider whether or no the VM is testable. If it is, then I know that I haven’t introduced any dependencies that I shouldn’t have. And even if it isn’t a fool proof way of limiting dependencies, it does help me…

More...