Ever wonder why the #nodejs community is embedding #rust into their code? Well check out the performance we are getting with embedding logos in QR codes without the canvas library. The first 3 are using #rust with NAPI. The slowest we get is when we push a large amount of data across the nodejs to rust boundary using buffer.
Just because #AI is writing your code doesn't mean you don't have to maintain it. Just think of all the lines it is writing, the modules / packages it is importing, all of that will need to be maintained. Learn the basics of how to do that with the language / environment you are using otherwise your going to have major issues in the future.
Using something like livesession.io is magical for understanding where your friction points are for your customers.
It's almost 2026 and we are still dealing with #commonjs vs #ESM issues in #nodejs. 2026 will be the last year that Keyv (https://keyv.org ) attempts to support commonjs with v6 due out this year. In 2027 we will move to ESM only with v7. It is just too painful to support commonjs compatibility.
This will also mean that `cache-manager`, `cacheable`, etc... will all move to ESM only in 2027. That is a large amount of caching usage across projects.
You can now set your default org and project via our CLI!
Start of the year coming up so it is time to re-read some amazing books and starting with Poor Charlies Almanac. https://www.amazon.com/Poor-Charlies-Almanack-Essential-Charles/dp/1953953239/ref=pd_bxgy_thbs_d_sccl_1/130-5348258-4381929
What other ones should I add to the queue?