Timeline for How do you know where you stopped in your codes after a 2-week break?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2019 at 12:08 | comment | added | Ivo | 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 | |
| Jun 21, 2019 at 10:45 | comment | added | Liath | 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 | |
| Jun 21, 2019 at 4:24 | history | answered | Euphoric | CC BY-SA 4.0 |