Gotcha, thank you for clarifying! Yes, this is a great point. We absolutely should continue to innovate and try new things and not be afraid to fail.
So maybe something I should help clarify is that when I talk about learning to stop making unforced errors, I don't mean to stop taking risks. Professionals in any field still make mistakes, and no one is infallible.
But thinking back to the analogy of amateur tennis vs. professional tennis, if we can learn from our past mistakes and stop hitting the ball into the net repeatedly, I think that is a good thing. As an experienced developer innovates and explores and takes risks, they would still be wise to apply lessons they've learned in the past so that they don't repeat the mistakes that they've made early on in their career.
Gotcha, thank you for clarifying! Yes, this is a great point. We absolutely should continue to innovate and try new things and not be afraid to fail.
So maybe something I should help clarify is that when I talk about learning to stop making unforced errors, I don't mean to stop taking risks. Professionals in any field still make mistakes, and no one is infallible.
But thinking back to the analogy of amateur tennis vs. professional tennis, if we can learn from our past mistakes and stop hitting the ball into the net repeatedly, I think that is a good thing. As an experienced developer innovates and explores and takes risks, they would still be wise to apply lessons they've learned in the past so that they don't repeat the mistakes that they've made early on in their career.
Added some general clarification here since I'm seeing a recurring theme in some of these comments! dev.to/thawkin3/comment/1iaka