Yes, I do.
Since I first saw that fluent and verbose semi-fluent API (Assert.That(actual, Is.Blah(...))
)I knew we were to become more than good friends. I saw potential in that relationship.
Yes, I do.
Since I first saw that fluent and verbose semi-fluent API (Assert.That(actual, Is.Blah(...))
)I knew we were to become more than good friends. I saw potential in that relationship.
A while ago I write about my then new gadget and gave some impressions to it.
It's been more then two months (time flies) and although I have not used it as extensively as I wanted to, I have some other opinions to share.
Gadget season.
There has always been something going on between gadgets and me.
Starting with the definition. What the hell is a gadget? What it the difference between a gadget and any other piece of technology you use or own?
Yesterday I found myself "in the need" to add some useful extension method to my tool-belt pet-project.
This project contains most of what I feel it's useful for general purpose development, including code that I borrow from the Internet (after careful unit testing) as well as my own utilities.
Continuing with the samples on patterns that make our development live a little more bearable and building on the shoulders of the not so giant previous post, we are going to face a very common problem: changing the behavior of an existing piece of code. Or putting it in another way, bending it to our purposes.