Comments on: TDD Tips http://blog.larsvonkconsultancy.nl/2009/07/tdd-tips/ Blogs about Software Development, Agility and all the Rest Tue, 24 Nov 2009 14:14:32 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: FitNesse Scenario are the Bomb « Vonk’s Blog http://blog.larsvonkconsultancy.nl/2009/07/tdd-tips/comment-page-1/#comment-116 FitNesse Scenario are the Bomb « Vonk’s Blog Fri, 31 Jul 2009 13:22:36 +0000 http://blog.larsvonkconsultancy.nl/?p=75#comment-116 [...] TDD Tips » In a previous blog on TDD I advocated that you should define your test on a high level. [...] [...] TDD Tips » In a previous blog on TDD I advocated that you should define your test on a high level. [...]

]]> By: Lonneke Dikmans http://blog.larsvonkconsultancy.nl/2009/07/tdd-tips/comment-page-1/#comment-39 Lonneke Dikmans Sun, 12 Jul 2009 12:52:56 +0000 http://blog.larsvonkconsultancy.nl/?p=75#comment-39 I totally agree with the first three statements. I have the same experience. The last one, however, is a self fulfilling prophecy: "Secondly in 99% of the applications the database is only a datastorage", is going to be true if you keep the database out as long as possible. Because you do the design in your refactoring. I think you should not keep any aspect out, and keep your options open: you can use a GPL like Java, or DSL like Drools or a PL/SQL. Also configuration and storage should be part of it. The requirements and experience of your developers and administrators determine the best solution, not <strong>just</strong> the developers. TDD is not the same as Java programming, or is it? I totally agree with the first three statements. I have the same experience. The last one, however, is a self fulfilling prophecy: “Secondly in 99% of the applications the database is only a datastorage”, is going to be true if you keep the database out as long as possible. Because you do the design in your refactoring.
I think you should not keep any aspect out, and keep your options open: you can use a GPL like Java, or DSL like Drools or a PL/SQL. Also configuration and storage should be part of it. The requirements and experience of your developers and administrators determine the best solution, not just the developers.
TDD is not the same as Java programming, or is it?

]]>