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 statement about books: If they're not out of date, then they're likely not good either. It takes a certain amount of time for good writers to get up to speed with a technology and then write a book about it.

Steven Evers
– Steven Evers

2010-10-29 22:46:45 +00:00
Commented Oct 29, 2010 at 22:46
2

I disagree a bit about the books. Look at Knuth, GoF, Effective Java and so on. Those books are about proven algorithms, patterns and idioms that stand the test of time. Books that just describe the current state of play of some framework, though, well they'll be pulp shortly enough.

Gary
– Gary

2012-07-03 11:19:44 +00:00
Commented Jul 3, 2012 at 11:19

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 »