That seems to be a great Idea to me.
I like this concept, for it seems practical
I've seen so many way of programming with a proven/therorical/formal design that were just unusable...
I REALLY like this method (paradigm?) beccause :
- The idea is simple (iterative 'enhance then check' step).
- The experience can be saved and transmitted (by describing refactoring recipe.)
- It seems that the process can be made partially automatic.
- It can be applyed to EXISITING project AND new ones.
However I'd definitly like to have more info on this (other links, books) and especially opinion of people who have been using it.
A step by step practical example of refactoring using Test
on an existing code would be welcome too...
Anyway, thanks for this info, I've never been so excited about a programming method for long...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||