You found the why. The reason to finish is smaller than you think.
csm18 wrote this under my last post, and it stayed with me all morning: "It became a normal thing for me to start a lot of projects and end with only 2 or 3. But your post made me think why? I now have the answer for why, but still need to find a reason for finishing a project. Maybe it's about learning to enjoy the process." He already has the why. Which is more than most people get. The harder…
A reader shared an insight about the importance of a reason to finish a project. It became clear that the usual advice to enjoy the process was insufficient. The writer noticed that their projects often remained unfinished, buried for months. The turning point came when a specific person insisted on receiving a project by a certain date.
The completion happened quickly, even poorly, simply because of the impending deadline and the need to show the person that the project existed. The writer suggested focusing on one human who would notice if the project didn't arrive, rather than generic notions like users or a portfolio. They recommended taking an almost completed project, writing down one name, and sending a brief message asking if the project is wanted by a certain time.
The response could either provide the reason to finish or reveal that the project never had a clear destination. The writer acknowledged that some people finish projects because the process is enjoyable, but emphasized that deadlines are crucial for projects without one. They admitted that their unfinished project is a case in point, and they wrote this to remind themselves to name the person who would notice.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
