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 for the complete toolchain. All the documentation in the world won't help if you can't build and test the software. When possible, I like to include the installation images for all the tools (although nowadays I'd probably opt for a VM image of some sort). Nothing worse than finding out the build process depends on a third-party plug-in from a company that doesn't exist any more!

TMN
– TMN

2012-08-28 16:01:49 +00:00
Commented Aug 28, 2012 at 16:01
@TMN - and that's why I tend to shy away from things like commercial IDE plugins and so forth. I don't trust that I'll be able to reproduce my environment later. And having worked on 20+ year old software, I NEVER assume that anything ever goes away.

Michael Kohne
– Michael Kohne

2012-08-28 16:16:50 +00:00
Commented Aug 28, 2012 at 16:16

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 »