You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
35Wow, THE Uncle Bob? It's great to get your thoughts here. I agree with you on the benefits of TDD, there really is no argument to be had there. The question is about the investment of time and the ROI. It isn't silly for me to consider these things. Imagine a project will take me 50% more time to finish with TDD than without, and the fairy tells me it will only save me 10% time over manual testing in the lifetime of the project. That might seem like a fantasy, but I see it as entirely plausible with certain projects.Ken Pespisa– Ken Pespisa2011-04-09 01:34:39 +00:00Commented Apr 9, 2011 at 1:34
-
14@Ken "Imagine a project will take me 50% more time to finish with TDD than without". That sounds EXACTLY like fantasy to me. In fact, it sounds like you just made that figure up on the spot without a shred of evidence to support it.Rein Henrichs– Rein Henrichs2011-04-29 05:11:08 +00:00Commented Apr 29, 2011 at 5:11
-
21@Rein Henrichs - Of course I made the number up, it was a hypothetical statement. I'm making the point that TDD adds a significant amount of time to a project, and I have to consider whether I'm going to get something of equal or better value in return. You don't have to convince me on the values of TDD, I'm convinced. But it is not a panacea.Ken Pespisa– Ken Pespisa2011-04-29 16:09:41 +00:00Commented Apr 29, 2011 at 16:09
-
15@Rein, what exactly is the "available evidence?" Please elaborate.Ken Pespisa– Ken Pespisa2011-05-23 22:15:47 +00:00Commented May 23, 2011 at 22:15
-
29@Uncle Bob "Replace the eyeblink with a few seconds": You are joking, of course. TDD is a good tool, but you have to test only the relevant parts otherwise you spend more time maintaining tests than doing any serious development. This is especially true when requirements are changing very quickly: you are constantly writing and throwing away tests for classes that change all the time. I am not saying TDD is bad, it must just be used sensibly and not applied mechanically as you seem to suggest.Giorgio– Giorgio2013-10-10 20:37:45 +00:00Commented Oct 10, 2013 at 20:37
|
Show 13 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you