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.

Required fields*

Rev

11

+1, there is no short-cut with this stuff. I would add that it is very important to have clear goals in mind. To "Completely understand and then 'improve' the design" is a very general and hard-to-define goal. It should be broken down into tangible problems/bugs/feature-requests.

Angelo
– Angelo

2012-04-29 13:14:05 +00:00
Commented Apr 29, 2012 at 13:14
1

+1 for the tests part.. writing tests is an efficient way to simulate and understand how the application/system flows..

Zuko
– Zuko

2015-01-15 07:10:47 +00:00
Commented Jan 15, 2015 at 7: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 »