Archives

Archives / 2008 / December
  • Recommended Reading

    I was asked a question today, what books I would recommend to read. Besides the those that I have already finished and a few that are still in pipeline, anything else that would contribute to the overall improving. The current list is:

  • Continuous Integration (book)

    First my personal impression - this book is a very good "business case" to introduceimage  things like automated builds, CI server, DB continuous integration (loved the word CDBI), automated deployment, automated inspection - most of the things that CI leverages. It doesn't go into deep details of one or another particular technology, balancing most of examples between (mostly) Java and .NET worlds.

  • Happy * !

    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 :)

  • Looking for Passionate Developers

    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.

  • Autumn Of Agile

    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!

  • Test-Driven Development: A Practical Guide

    This book is a bit outdated (published in 2003, probably written in 2002), but still one of the best practicalimage  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. 

  • "Hello World" TDD Style

    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.

  • First Milestone

    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.