lancerkind

8 ms·

61.
by lancerkind 9y ago
Thank you for that. I've got the idea now. In these projects, are you responsible for the maintence and later code changes? Or are these projects one time deliveries and someone else handles things from then on? Also, if you don'
62.
by lancerkind 9y ago
I'm curious how much time was spent trying to write test driven code before deciding it wasn't working for you. Did you succesfully write a few small programs using TDD (coding katas)? Or did you apply TDD to your project at work?
63.
by lancerkind 9y ago
I'm interested in your test later approach. When you're attempting 100% branch coverage, do you sometimes find writing the test later causes redesign of the product code? On average, how many days does it take to complete a cycle
64.
by lancerkind 9y ago
Thanks for the TDD study reference. I collect these and I haven't seen that one.
65.
by lancerkind 9y ago
How was TDD presented/introduced to you?
66.
by lancerkind 9y ago
Regarding coverage comment, your right in that code can contain capabilities (or bugs) beyond the TDD coded conceived. (If they weren't conceived then it could be a bug or things that don't happen in practical operations.) The TDD
67.
Developers, confess why you don't TDD(confessionsofanagilecoach.blogspot.com)
3 points by lancerkind 9y ago|15 comments
68.
by lancerkind 15y ago
It's the same: successfully giving them the goods and service they want (laughs, a cool website, a web API). Being able to identify what interests them during a conversation is a master skill. Let me say it another way: if you have a great
69.
by lancerkind 15y ago
The process of explaining something is very valuable. As a science fiction writer, when I tell someone a summary of a story I wrote, I can read in their expression or verbal "uh huhs" what's drawing them in and what's distraction from the h