Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
Loved this article. and loved the parallel with Ping Pong.
I always found that we developers have a tendency of shoot ourselves in the foot by underestimating tasks, overengineering solutions or simply by focusing on wrong things ( cure the symptom of a problem and not solve the root cause).
Expecially loved you list of unforced errors and i could not stress more on the first one:
Not understanding the problem before trying to code a solution
Too many time I have seen team members diving head first into coding something without previously properly thinking about the problem, understanding the context and the scope, coming up with a couple of alternatives and discussing them with other peers, and instead find themselves with a rejected merge request days or weeks later..
Thanks for sharing
Loved this article. and loved the parallel with Ping Pong.
I always found that we developers have a tendency of
shoot ourselves in the foot by underestimating tasks, overengineering solutions or simply by focusing on wrong things ( cure the symptom of a problem and not solve the root cause).
Expecially loved you list of unforced errors and i could not stress more on the first one:
Too many time I have seen team members diving head first into coding something without previously properly thinking about the problem, understanding the context and the scope, coming up with a couple of alternatives and discussing them with other peers, and instead find themselves with a rejected merge request days or weeks later..
Thanks for sharing
Thank you Davide! Those are some great additional items you've identified to add to our list of unforced errors.