Hi Daniel, I believe the point of the analogy is that "tests can't do the thinking for you". In that sense, a strict TDD workflow where you think only about the very next test might be undesirable. In case you didn't read it, this article explains it much better: http://patrick.lioi.net/2011/11/23/guard-rail-programming/
Sebastian On Wednesday, March 25, 2015 at 3:53:44 AM UTC+1, Daniel Hinojosa wrote: > > What is TDD culture in Clojure like? Is it strong in the community and > other projects? I am aware of Rich Hickey's guard rail analogy. Did that > have an effect on how Clojurists view TDD or testing in general? Just > asking for my own personal research. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
