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
agree. and in fact, even though all the team was on the same page about the necessity of having that framework everywhere, it was a mistake doing it at once on my own.
regarding changes to small parts of code, again, it depends on how small, and what you mean with "changing" them.
adding a unit test, rename a method, fix a typo, splitting big methods to make them more testable, and understandable, does not disrupt the code base not the coding experience of your colleagues.
agree. and in fact, even though all the team was on the same page about the necessity of having that framework everywhere, it was a mistake doing it at once on my own.
regarding changes to small parts of code, again, it depends on how small, and what you mean with "changing" them.
adding a unit test, rename a method, fix a typo, splitting big methods to make them more testable, and understandable, does not disrupt the code base not the coding experience of your colleagues.
but i agree with you, everyone should be aware. about this Dan Abramov shared a very nice experience of a code refectoring mistake he did in the past