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

This IMHO is the right answer. Your project is made up of lots of little parts, you should aim to finish each one before taking a significant break and moving onto the next. In other words... scrum

Liath
– Liath

2019-06-21 10:45:41 +00:00
Commented Jun 21, 2019 at 10:45
I agree with this. keeping the tasks small enough that they can be done in a day or less seems to be the generally accepted practice. Having this guideline makes the problem stated a non-issue

Ivo
– Ivo

2019-06-21 12:08:55 +00:00
Commented Jun 21, 2019 at 12:08

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 »