In this episode, Isaac and Jeffrey discuss falsehoods that programmers believe about projects. They explore assumptions such as projects having defined beginnings and endings, the role of priorities in project work, and the importance of clear communication and feedback. They also touch on the challenges of working on successful projects that transition into ongoing maintenance and the consequences of failed projects that continue to exist. The conversation highlights the need for programmers to question these assumptions and adapt their approach to project management.
This episode is a supplement to my post about Falsehoods Programmers Believe About Projects.
Takeaways:
- Projects often don’t have defined beginnings or endings, and assumptions about their start and end dates can lead to confusion and miscommunication.
- Relying solely on personal priorities to determine when to start working on a project can lead to conflicts and misunderstandings with others who have different priorities.
- Clear communication and feedback are crucial in project work to ensure everyone is on the same page and to avoid missed signals and mixed signals. – Programmers should be proactive in sharing their expertise and insights on projects, even if they haven’t been explicitly asked, to prevent unnecessary rework and improve overall project outcomes.
- Successful projects often transition into ongoing maintenance and feature development, while failed projects that are not fully turned off can continue to exist and incur costs.
- Questioning assumptions and adapting project management approaches based on the specific context and circumstances of each project is essential for success.
Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!
