This is a good point, and I think we could write some much longer posts on some of these practices.
I appreciate how this points out how important the "why" is of many of these patterns and practices.
I've been developing in JS since nearly the beginning and many of these "best practices", that are somehow still mainstream, are for problems that no longer exist.
Since people often don't know why we did them, they continue to persist them because all the Sr. Devs told them to years ago.
I've been developing in JS since nearly the beginning and many of these "best practices", that are somehow still mainstream, are for problems that no longer exist.
Since people often don't know why we did them, they continue to persist them because all the Sr. Devs told them to years ago.
This is so true of so many areas of software development. Workarounds become best practice and stay that way long after they are needed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a good point, and I think we could write some much longer posts on some of these practices.
I appreciate how this points out how important the "why" is of many of these patterns and practices.
I've been developing in JS since nearly the beginning and many of these "best practices", that are somehow still mainstream, are for problems that no longer exist.
Since people often don't know why we did them, they continue to persist them because all the Sr. Devs told them to years ago.
The "why" is so important to know.
This is so true of so many areas of software development. Workarounds become best practice and stay that way long after they are needed.