The speaker shares their reasons for avoiding tools like GitHub Copilot, emphasizing that manual coding fosters deeper engagement and understanding, which are essential for their growth as a programmer. They express concerns about increased bugs and diminished learning opportunities for beginners when relying on automated code suggestions, ultimately advocating for the benefits of active involvement in the coding process.
In the video, the speaker shares their personal perspective on why they choose not to use tools like GitHub Copilot while programming. They emphasize the importance of being fully engaged in the coding process, noting that writing code manually allows them to focus on each line and understand the logic behind their work. This engagement is crucial for their learning and development as a programmer.
The speaker describes a specific behavior they exhibit when using Copilot: they often pause to wait for the tool to complete their code suggestions. This waiting period disrupts their flow and diminishes their active involvement in the coding process. They express concern that relying on Copilot leads to a lack of engagement, which ultimately affects the quality of their work.
Another significant point made is the increased likelihood of encountering bugs when using Copilot. The speaker reflects on their experiences, stating that they have faced more issues when using the tool compared to when they code independently. They attribute this to a decreased level of attention and care when allowing Copilot to generate code for them.
The speaker also addresses the implications of using Copilot for new programmers. They advise beginners to avoid relying on such tools, as it can hinder their learning experience. By depending on Copilot, novice programmers may miss out on essential opportunities to learn syntax and develop problem-solving skills, which are vital for becoming proficient in coding.
In conclusion, while the speaker acknowledges that Copilot can be a helpful tool at times, they ultimately view it as detrimental to their programming practice. They believe that the benefits of manual coding—such as deeper engagement and better understanding—far outweigh the convenience offered by automated code suggestions. Their stance highlights the importance of active learning and personal involvement in the programming journey.