Timeline for How do I deal with the "30 minutes remaining" problem?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 24, 2017 at 11:41 | review | Suggested edits | |||
| Apr 24, 2017 at 12:25 | |||||
| Apr 24, 2017 at 9:07 | comment | added | Luaan | That's the last thing I would want to do at the end of a day. If your unit tests are perfect, and you never introduce a change that takes more than a minute or two, and you don't introduce merging issues... maybe. Just considering possible improvements (and planning for them if they seem worthwhile) seems to carry less cost to me, and seems to be just as effective in the long run. The hardest bit is overcoming the inherent brain-inertia in even considering the costs and benefits of any change. | |
| Apr 23, 2017 at 18:24 | history | edited | Timothy Truckle | CC BY-SA 3.0 |
added 144 characters in body
|
| Apr 21, 2017 at 19:13 | history | edited | Timothy Truckle | CC BY-SA 3.0 |
added 102 characters in body
|
| Apr 21, 2017 at 19:11 | comment | added | Timothy Truckle | @jpaugh "+1 Taking a few minutes to think about the quality of your work" Thanks, but why not doing it? As written it is safe and fast. | |
| Apr 21, 2017 at 17:04 | comment | added | employee-X | +1 Taking a few minutes to think about the quality of your work (let alone actually improving it) is a very professional thing to do! In fact, it's required for professional growth. | |
| Apr 21, 2017 at 16:34 | history | answered | Timothy Truckle | CC BY-SA 3.0 |