sfeldman.NET

Write your test code as you would write your production code. In my opinion, a few of the most critical things are:

After reading “Implementing Lean Software Development: From Concept to Cash”, I decided to look at the original book. It is as good as the successor. IMO reading the original one first even better than just skipping to the new version.

Found this great excerpt in a book:

I have finished reading the book and wanted to write a short review, but the best I could come up with is a list of cons and pros. Lame, I know, but this will give you a hint at least.

I was chatting with an old mate of mine, Lev  Ozeryansky, with whom we graduated together computer science about 8 years ago (man, that was long time ago, but doesn’t feel like that). He’s a great developer, with lots of experience. Yesterday we have finally met and chatted a bit (guess about what). Two things I heard bothered me a lot.

On my flight I had a chance to finish reading “Code Leader” by Patrick Cauldwell. The book is a good source for ideas and concepts that “solid” developers should employ on a daily basis. Topics such as TDD, build vs. buy, CI, choosing the right tool for the right job, contract driven development, and much more.

I am on my vacation, and not suppose to brag about software, but something has happened on my way to Israel, that just couldn’t go away silently. To get from Calgary to Tel-Aviv, I had to fly with Lufthansa for 9 hours first. The Airbus 340 is a decent plain. It’s flying, and it’s as comfortable as a Economy class can be. What blew me away was the entertainment system. Let me break this down.