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.

That has indeed proven to be a major hurdle for me to understand the flow. This example is quite small, but another one used 35 (!) instance variables for its intermediate results, not counting the dozen instance variables containing the dependencies. It was quite hard to follow along, as you have to keep track of what has already been set earlier on. Some were even reused later on, making it even harder. Luckily the arguments presented here have finally convinced my colleague to agree with refactoring.

Alexander
– Alexander

2019-03-14 15:52:52 +00:00
Commented Mar 14, 2019 at 15:52

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 »