10 regrets of experienced programmers

The video discusses common regrets of programmers, emphasizing the importance of writing less code, learning to code earlier, and finishing more projects. It also highlights the need for physical health awareness and the potential disillusionment with the tech industry, ultimately questioning the value of programming as a meaningful career.

• Programming is unique in that it offers countless paths and opinions, but many developers regret writing too much code, as it becomes a liability rather than an asset that requires future maintenance.
• Learning to code earlier can significantly enhance one's career prospects, as younger individuals tend to learn more efficiently and may face less age-related bias in the tech industry.
• Finishing more projects is crucial; many developers underestimate the time and challenges involved in completing software projects, often regretting the many unfinished endeavors they leave behind.
• Obtaining a computer science degree can provide valuable networking opportunities and is often a requirement for certain jobs, even though practical experience is also critical for learning to code effectively.
• Prioritizing health is essential for programmers, as a sedentary lifestyle can lead to serious health issues; taking breaks, using standing desks, and maintaining a good diet can greatly improve overall well-being and productivity.

• Regret number one highlights the misconception that more code equates to better programming. The speaker emphasizes that code should be viewed as a liability rather than an asset, as more code increases maintenance challenges and potential for errors. Beginners may struggle to write code, but as they gain experience, they often realize that simplicity is key. The speaker reflects on their own regrets about overcomplicating code in the past, underscoring the value of writing less and maintaining simplicity to enhance productivity and reduce future burdens.
• In regret number two, the speaker discusses the advantages of learning to code at a young age, arguing that younger individuals have a greater capacity for learning. They note the presence of ageism in the tech industry, where younger programmers are often favored. While it's possible to learn coding at any stage of life, the speaker emphasizes that starting young can lead to significant career advantages. They humorously suggest that the best time to start coding is in the womb, but the second-best time is now, encouraging those interested to begin their learning journey immediately.
• Regret number three reflects on the common struggle of finishing software projects. The speaker introduces the '90-90 rule', which states that when a developer feels a project is 90% complete, they often have another 90% of work left. They acknowledge their own tendency to abandon projects and start anew, leading to regrets over time wasted on unfinished work. However, they also stress the importance of recognizing when a project isn't worth completing, as sometimes knowing when to quit can be more beneficial than pushing through to a finish.
• In regret number four, the speaker contemplates the value of obtaining a computer science degree. They argue that while real-world experience may provide more practical learning, a degree can facilitate networking opportunities and access to better job prospects in tech. The speaker warns against pursuing degrees that don't lead to job opportunities, humorously referencing degrees in Egyptian studies as an example. They conclude that while a degree isn't strictly necessary, it can open doors that may otherwise remain closed.
• Regret number five reveals the speaker's lament over not investing in Bitcoin earlier, highlighting the dramatic financial gains that could have been achieved. They illustrate this point with a hypothetical scenario of turning a small investment into millions. This regret serves as a reminder of the unpredictable nature of investments in tech and finance, and the potential for significant loss when opportunities are missed. The speaker finds some solace in knowing others may have made even bigger mistakes, such as losing hard drives containing their Bitcoin wallets.
• In regret number six, the speaker discusses the importance of learning lower-level programming languages like C. They argue that while many programmers start with high-level languages, understanding lower-level concepts can enhance overall programming skills and provide a strong foundation. The speaker reflects on their own learning path and expresses a desire to have started with C, as it would have better equipped them for their coding career. They encourage aspiring developers to consider learning lower-level languages to improve their coding proficiency.
• Regret number seven addresses the use of JavaScript on the server. The speaker defends their choice to use JavaScript across the entire tech stack, citing the benefits of faster development and iteration despite the language's limitations in terms of efficiency and type safety. They express satisfaction with their decision to use JavaScript on the server, underscoring the flexibility it offers in various applications, from web to mobile and beyond.
• In regret number eight, the speaker reflects on their experiences preparing for technical interviews at major tech companies and their time spent practicing algorithms. They express regret over the hours invested in platforms like LeetCode, noting that brute-force solutions often led to minimal learning outcomes. This regret underscores the idea that while technical interviews are important, the focus on algorithms may not always align with practical programming skills that are more relevant in real-world applications.
• Regret number nine emphasizes the importance of prioritizing health in a sedentary profession like programming. The speaker warns about the long-term health risks associated with a desk job, such as heart disease and obesity, and advocates for lifestyle changes like using standing desks and taking breaks. They argue that physical health directly impacts mental acuity and productivity, suggesting that maintaining well-being is crucial for long-term success in programming.
• Finally, regret number ten captures a sense of existential reflection on the impact of a programming career. The speaker expresses a feeling of dissatisfaction with the nature of their work, likening it to creating 'vaporware' for superficial metrics rather than contributing to meaningful change. They contrast their experience with more tangible professions, such as teaching or emergency services, which offer a sense of fulfillment. This regret conveys a broader contemplation on career choices and the search for purpose beyond technical achievements.

• Code is a liability, not an asset; prioritize simplicity in programming to reduce future maintenance.
• Learning to code early gives a significant advantage due to the brain's optimization for learning; start coding now if you haven't already.
• Finishing projects is crucial; many developers regret not completing theirs due to unexpected challenges and distractions.
• A computer science degree can enhance job prospects and networking opportunities, even if not strictly necessary for coding jobs.
• Investing in Bitcoin early could have yielded significant returns; regret missing out on such opportunities is common among developers.
• Understanding lower-level languages like C can provide a strong foundation for programming, even if starting with high-level languages is common.
• JavaScript's versatility across different platforms is beneficial; using it on the server can accelerate development despite some inefficiencies.
• Practicing algorithms on platforms like LeetCode often leads to frustration and may not be the best use of time for some developers.
• Prioritizing physical health is essential for long-term well-being in a sedentary job; consider using standing desks and taking regular breaks.
• Despite the satisfaction from coding, some developers regret not pursuing careers that feel more impactful or real.

• The narrator volunteered at a hospice center and posed a thought-provoking question about programming regrets, highlighting that programming is unique due to its many possible paths and conflicting opinions.
• The first regret discussed is the wish to have written less code, emphasizing that code is a liability that requires maintenance and can break applications. The speaker reflects on the realization that simplicity in coding often leads to better productivity.
• The second regret is about learning to code earlier, as younger individuals have a better capacity for learning. The narrator notes the prevalence of ageism in tech, where younger programmers are often preferred due to their more adaptable minds.
• The narrator promotes a Chrome plugin called Daily Dodev, which helps developers stay updated on industry news and network with other developers, stressing its value as a free resource for the programming community.
• The third regret revolves around not finishing enough projects, with the narrator sharing personal experiences of starting but not completing many projects. They mention the '9090 rule' that indicates the last stages of a project often take much longer than expected.
• Regret number four highlights the desire to have obtained a computer science degree. While acknowledging that a degree isn't strictly necessary for a tech career, the narrator points out that it can provide valuable networking opportunities and job security.
• The fifth regret is about not investing in Bitcoin when it was first introduced, illustrating how a small investment could have resulted in substantial wealth today. The narrator finds some solace in the struggles of those who lost their Bitcoin investments.
• The sixth regret addresses the importance of learning lower-level languages like C, which provide a fundamental understanding of programming. The narrator believes that starting with high-level languages can limit a programmer's foundation.
• The seventh regret is about using JavaScript on the server. The narrator expresses no regrets about utilizing JavaScript across various applications, despite acknowledging its limitations in terms of efficiency and type safety.
• Regret number eight discusses the time spent practicing algorithmic challenges on platforms like LeetCode, which the narrator feels was not the best use of their time, especially considering their ultimate career achievements.
• The ninth regret emphasizes the importance of prioritizing health, as a sedentary lifestyle combined with stress can lead to severe health issues. The narrator recommends solutions like standing desks and breaks to mitigate health risks.
• The tenth regret reflects on the existential question of whether learning to code was worthwhile, expressing envy for professions that feel more 'real' and impactful compared to the often abstract nature of programming work.