On Feb 4, 2014, at 6:06 AM, Jay Fields <j...@jayfields.com> wrote: > - REPL driven development, putting TDD's 'rapid feedback' to shame.
Pity I'll miss this, but I only come up to Chicago W-F. What I've found is that having autotest in the REPL dissolves most conflict between TDD and REPL-driven development. Or to put it differently: having a REPL autotest makes writing a test less hassle than working in the repl - maybe 80% of the time. In the other 20%, the REPL is invaluable, though I always grate at the need to then "immortalize" the core of what I did in the REPL in repeatable tests. (Actually, making clear distinctions like "80% doing this vs 20% doing that" feels like a poor reflection of my lived experience. I spend my time with four emacs windows open: a repl, the source, the tests of the source, and the miscellaneous window. I move very fluidly between them. Whatever source-of-immediate-gratification works best in the moment is always ready-to-hand.) -------- Latest book: /Functional Programming for the Object-Oriented Programmer/ https://leanpub.com/fp-oo -- 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/groups/opt_out.
