3 ms·
For me, this cycle is a different one: (Step 0 is possibly 'get a bug report') 1. Write a test 2. Watch the test fail 3. Write code 4. Watch the test pass
by jaggederest 14y ago
For me, this cycle is a different one:
(Step 0 is possibly 'get a bug report')
1. Write a test
2. Watch the test fail
3. Write code
4. Watch the test pass (if fail, goto 3)
5. Make the code pretty
6. Watch the test pass
7. Repeat
Instead of negatives, you're looking for positives. At the end you're rewarded with nicer code than you started with and green lights all the way down.
It's all about how you frame it - why would you frame the activity you spend most of your life doing negatively?
- indiecore 14y ago>6. Watch the test pass 7. Send it to QA. 8. Everything is wrong and this isn't what they asked for (it is but that's not what they MEANT) 9. Goto 3
- jaggederest 14y agoNo, you GOTO 1, and write new tests that match better. Just because you have a dysfunctional organization that doesn't let QA and development talk doesn't mean that's how it has to be.