re: Investing in the right technologies to avoid technical debt VIEW POST

TOP OF THREAD FULL DISCUSSION
re: I really like this article! Especially with the heading "Learn patience, not a new framework" I suggest every developer to spend some time learnin...
 

Thank you, that means a lot. I'm quite proud of that heading honestly.

Completely with you on risk & reward. You don't want to introduce too high of a risk if the reward isn't great. This is why incrementally introducing changes makes for an ideal compromise, especially in preparing for an eventual framework change when needed.

 

:). Looking forward to more of your writings.

I would also add that I think there is an unspoken amount of entropy that it takes to get new developers to utilize a new tool + practice. This should also be included in risk assessment of introducing a new tool.

One of the worst things that can happen is that your software is filled with various tools that various people. Bloat :O

Either that or developers creating their own utilities that duplicate existing functionality, simply because they don't like the current solution or didn't know it existed. This is of course mostly a problem in larger codebases but still plays to your point, installing a library is simply step 1 to adoption/integration.

code of conduct - report abuse