People often say that JS (and implicitly NodeJS) is confusing because of its magic power. Moreover, JS landscape changes over time and changes fast.
That is something one should accept if one is doing JS. Nobody uses call-backs anymore, for instance, and even promises are not explicitly declared most of the time.
There are a lot of frameworks and a lot of packages one can use - especially on the frontend.
One project can be completed in several entirely different stacks, and each stack might be different enough that we, developers, can not switch between them easily.
The end result, however, is that nobody from QA, management or the customer would see (nor care) about the differences between using the different stack - the results would be similar enough.
Speaking of constant change. An excellent place to understand how to deal with change, solve old (architecture, e2e testing, dev tools, etc.) and new (accessibility, Typescript integration, AI-chatbot adoption, etc.) problems are to get insights from different applied approaches throughout JS conferences.
revo.js is one of them! And they specifically focus on the ever-changing nature of software development! Don't miss out and get your regular discounted ticket with the promo code:
(there are only two days left for the regular tickets)
Photo by timJ on Unsplash
(open source and trusted by devs everywhere ❤️)