Edit - Software Engineering Stack Exchange

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.

+1 TDD is feedback. As most measures of feedback go, it's fairly objective and completely automated, so it can be shared by team members of all skill levels. Before TDD, good code was something you "felt", or was confirmed sometime after the users got the software. The shorter the loop, the more confident you feel. Unfortunately TDD is prone to overconfidence as "feeling" a good design, but it's far easier to self-correct.

Steve Jackson
– Steve Jackson

2011-08-23 16:29:27 +00:00
Commented Aug 23, 2011 at 16:29

Add a comment |

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

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>

formatting help »
answering help »