The thesis of this article is “you have to finish strong, every time.” The author strongly emphasizes that the work at the end of a software development project is just as important (if not more so) than the work at the earlier stages of the project. She cites what is known as the peak-end rule, where the closest recall and strongest emotions (such as what will be recorded in a performance review) happen last. Yet motivation and energy tend to be low near the end of a project, and the work can be more boring, such as bug fixes and documentation. The author states that you have to make a great finish a priority, and you can do this by big-picture thinking, making the unglamorous a priority, and channeling your ability to keep going.

This short, clearly written article should be a priority read for any software developer who has experienced the challenge of trying to finish a project strong (which should be nearly every developer).