3 ms·
I once had an interview with Pivotal labs in which I paired with their devs to do some TDD. We spent about 20% of the time writing code and 80% writing tests an
by samjohn 16y ago
I once had an interview with Pivotal labs in which I paired with their devs to do some TDD. We spent about 20% of the time writing code and 80% writing tests and fixing bugs in the test cases. I can see how it works for what Pivotal does but this would definitely not fly when you're trying to ship and iterate as fast as possible.
- bigiain 16y agoKeep in mind that sometimes the alternative is to spend 20% of the time writing code, and 80% of the time fixing bugs that made it into the live environment and are affecting customers. I think one of the hard decisions to time correctly when a startup gains traction is "when do we stop being cowboys, and adopt proper development practices?". I see (in mysef as well as others) _way_ too much clinging to the "Oh, I' just ssh into the live server and fix that" kind of behaviour, often way past the point where that's clearly no longer the right way to proceed... (and yes, I bit myself with that just last week, again... Ouch!)
- jayunit 16y agoyour first sentence: nail, head.