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

This thread as a whole has been very helpful, but indeed the first paragraph here is very true. Mostly what I have learned since implementing these directions is that the code will evolve - rapidly. Although I started out with 1 theory of a direction, I went through several structures, tweaking here and there, before I came up with something that works well, feels right, and, has little to do with the original blueprint I had down on paper. Something did indeed emerge. Maybe a topic for another post, but how does a programmer learn to best deal with code evolution? Is this 'refactoring?'

user66662
– user66662

2012-10-14 00:34:05 +00:00
Commented Oct 14, 2012 at 0:34

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 »