I kind of follow a similar principle here. Many times I will write app
code because in not sure how to pull of the functionality I'm try to
do. Once I can confirm that I'm getting the expected results, I take a
mental note of what I did, remove the code, and drive it out again
with the spec.
I like this method a lot because the repetition helps me to lock in
the logic. Kinda like how people say you really know a topic if you
can teach it to someone else. The spec almost because that someone
else I'm teaching.
So in short, I think you're safe in your approach, but don't leave the
code-first spec-second code in production.
--------------
Frank Lakatos
Catchon Media
[email protected]
http://www.catchonmedia.com
On Feb 19, 2010, at 7:21 AM, Matt Wynne <[email protected]> wrote:
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
