sfeldman.NET

I realized that I always forget to greet the readers. Never too late to fix it (and yes, I have a test in place to automate it from now on :)

Our team is growing and we are looking for passionate developers that go beyond the average. If you are looking for an environment that is all about software development, agile flavour, thinks out of Container, T/BDD spiced, .NET mixed with OSS, mapped with NHibernate, and willing to go beyond, then it's the place to join. We are located in Calgary (Canada) and will be happy to have you on board. Who is interested, can drop me a note at Feldman {dot} Sean {dot} at gmail {dot} com.

Stephen A. Bohlen has started a great series of screencasts. You should definitely check it out if you are into Agile and the rest. The work is really done well, so donate!

This book is a bit outdated (published in 2003, probably written in 2002), but still one of the best practical  examples of what TDD is all about. It talks about unit testing, mocking, integration testing. I am definitely putting this one on my recommended readings list. The part I loved is that the author takes readers from zero to an application implementing not just the back logic, but also the UI, all TDD done. The nice transition from state testing to mocking was very well performed, and in MHO one of the best I have seen so far in books. 

A friend of mine told me, "what you know and what seems to as trivial, might be completely new to someone else". So I am trying to remember this, and once again the simple life wisdom proved to be correct. One of our team members had to be away while the team was conquering T/BDD and unit testing. As a result, he stayed a little behind, and as catch up exercise, we pared on a very simple problem, Calculator, another version of the classical "Hello World". Maybe this will help someone someday.

I learned from a wise man that celebrating small successes as important as the having big one, if not even more. So today I would like to thank my team for the effort they made in such a short period of time and with a quiet a steep learning curve they had to go through. One picture is worth a thousand words.

C# 3.0 has introduced lots of great features to make our life easier and syntax sweeter. Lots of people talked about it already, and I am not scooping here anything new. What I do want to demonstrate, is how to make the code easier to understand.

Today was a great day. One of the things we do with the team is experiment how we write our test. Experimenting seems the most effective way of figuring out what should be our testing approach. At this point we are mostly doing specification driven tests (unit tests).