Comments on: Unit testing in Coders at Work

By: Global Day of Code Retreat | Coding Is Like Cooking

Global Day of Code Retreat | Coding Is Like Cooking — Wed, 08 May 2013 09:33:16 +0000

[...] “you can test all you want and if you don’t know how to approach the problem, you’re not going to get a solution” (from Peter Siebel’s book “Coders At Work”, an extract of which is available in his blog) [...]

By: Quora

Quora — Sat, 20 Oct 2012 02:49:24 +0000

Is it worth it becoming a software engineer?…

If you visit the top schools, you’ll see that there’s no distinction set between a software engineer and a computer scientist. Every course 6 graduate from MIT is both a computer scientist and an engineer. The same goes for Berkeley, Stanford, etc. W…

By: The value of DOING for the CIO: test-driven development

The value of DOING for the CIO: test-driven development — Thu, 30 Aug 2012 18:59:32 +0000

[...] Seibel, “Unit testing in Coders at Work“, October 5, [...]

By: PK

PK — Tue, 27 Sep 2011 01:09:03 +0000

Peter – From what I have learnt about TDD. It is awesome if you are building an enterprise software. But not otherwise. In the example you have mentioned Norvig was trying to solve a puzzle. TDD will work great if your aim is to display data on the web page from the database. That is pretty much the reach of TDD. You wont be able to solve complicated problems like building a search engine by thinking about it from a TDD angle. I doubt if Google has set of unit test cases for their search engine. I think there are two types of philosophies – design pattern philosophy and the algorithm functional programming philosophy. I have rarely seen a design pattern guru being an expert in algorithms etc or vice versa. Norvig is an algorithms guru, he is not going to like TDD.

By: haji

haji — Fri, 19 Aug 2011 08:52:50 +0000

where can i get like lisp tutorials (videos)

By: Enzo

Enzo — Tue, 31 May 2011 22:37:21 +0000

TDD slows you down for sure. Now you have to maintain your regular code and your test code base and refactor both constantly. Usually any bug found can be fixed quicker than maintaining all of this test code. No modern company like Ebay, Amazon, Facebook, Google, Zappos, etc. would even exist if they wasted time on TDD up front.