The Graveyard of Repos: 100 Projects - Zero Shipped

Many software engineers struggle to finish projects, accumulating digital graveyards of unfinished work. The initial excitement of starting projects often fades, replaced by the difficulty of completing them. This transition from starting to shipping is a significant hurdle, involving a shift in perspective on what "done" means. Several factors contribute to this, including the "creation high," lack of a clear "definition of done," and the allure of new technologies. Other reasons are perfectionism and the fear of judgment. To overcome this, redefine “done” using the Minimum Viable Ship (MVS) approach that prioritizes a single core feature and public deployment. Utilizing a "one-user" rule and deploying a basic version to a public URL are essential. Use mental models like Parkinson's Law and the 15-minute rule to stay focused and combat procrastination. Embrace Type 2 decisions and prioritize quick choices for initial aspects. Focus on a “Finish One” protocol, which involves inventorying projects and ruthlessly archiving inactive ones. Pick one project and break down the remaining tasks into small, manageable steps. Build systems that prioritize completion and embrace boilerplates and automation. Recognize that unfinished projects provide valuable learning experiences. View abandoned projects as tuition in continuous learning and experimentation. This allows you to leverage acquired skills. You should also choose one project and define its MVS to ship a product.