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

4

Would you care to summarise for those of us who don't own the book?

Kramii
– Kramii

2011-08-16 05:52:34 +00:00
Commented Aug 16, 2011 at 5:52
I agree with Kramii. A summary would be great!

Vaccano
– Vaccano

2011-08-16 18:09:59 +00:00
Commented Aug 16, 2011 at 18:09
@Kramil, Vaccano, It looks like I'll have to check it out of the library again. Normally I only do so when starting a new job and discussions turn to naming and coding standards.

Tangurena
– Tangurena

2011-08-16 19:39:46 +00:00
Commented Aug 16, 2011 at 19:39
1

lol, so "One cannot depend upon differences in case alone to distinguish items", then goes on to say use camelCase or PascalCase to differentiate items.

gbjbaanb
– gbjbaanb

2013-07-20 22:38:40 +00:00
Commented Jul 20, 2013 at 22:38

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 »