This is an interesting book to read in case your reading queue is empty
and you want to brush up some aspects of C# (2/3). I can’t recommend this book as a general reading, as it’s way too narrowed to specific subjects (or implementation of those). Saying this, I really loved the introduction into expressions and functional pieces in C#. It gives you the hint what’s going on, leaving a taste of more to read.
I am happy to welcome David Morgantini, who has joined our team. Adding another solid developer into our team is definitely the right step. This is going to be an exciting journey for all of us.
Good luck, David.
So today is the day. I am 31 and a new iteration in my life has started. What are the features I am trying to achieve in this one? A few:
And more than ever - “Never give up, never surrender”.
Davy Brion "The Life And Times of a Bug" post.
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:
The order doesn’t really matter, though I would strongly recommend to read the first 5-6 books first, with “Who Moved My Cheese” in the middle. Other good books that you find useful - please feel free to recommend. If you are into Agile methodology, “The Art of Agile Development” and “Pair Programming Illuminated” are probably the best two starters.
First my personal impression - this book is a very good “business case” to introduce
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.
From my personal experience, if your company doesn’t practice CI in any shape or form and shows no interest in it, using excuses like “we deploy internally”, “our deployment consist of a few assemblies and content files”, or worse “there’s no real benefit in it” - think twice if you are in the right place and do your math.
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 :)
Happy Chanuka, Cristmas, and New Year!
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.
