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.

The Feathers book is an excellent one indeed - for unit testing and maintaining legacy code. Since the question is about new code, it may not be of much direct value here though.

Péter Török
– Péter Török

2011-10-23 20:59:01 +00:00
Commented Oct 23, 2011 at 20:59
@PéterTörök Yes, fair point. The question is about new code. On the other hand it also mentions cleaning up existing code. With commercial products where the impact can be devastating I believe it is important to be extremely careful. Hence my mentioning the book.

Manfred
– Manfred

2011-10-23 21:10:35 +00:00
Commented Oct 23, 2011 at 21:10

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 »