TDD only works correctly if you have an exact specification of the solution. It is not good in an agile context where everything is unclear or unknown at the beginning.
The NPM ecosystem is broken because of the massive dependency hell and breaking changes every six months.
Just because Async code is good on the client side (browser) doesn't mean it's the right approach for the server side. Even the DOM manipulation is synchronous, for good reasons. Async is like a hammer you want to apply to everything, even if it doesn't make sense in every case. People should begin to distinguish more carefully when, where and for what Async IO is better or worse suited.
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.
Unpopular software opinions:
TDD only works correctly if you have an exact specification of the solution. It is not good in an agile context where everything is unclear or unknown at the beginning.
The NPM ecosystem is broken because of the massive dependency hell and breaking changes every six months.
Just because Async code is good on the client side (browser) doesn't mean it's the right approach for the server side. Even the DOM manipulation is synchronous, for good reasons. Async is like a hammer you want to apply to everything, even if it doesn't make sense in every case. People should begin to distinguish more carefully when, where and for what Async IO is better or worse suited.