Before answering that question, I'd go back to the roots of the KonMari method. "Sparking joy" is an imperfect translastion from Japanese, says redditor:
Long and short of it, ときめく(Tokimeku) is a compound verb by "Toki" and "meku", where "Toki" is derivation of "Dokidoki" (Heart pounding) according to the two main Japanese dictionary. Full meaning :
Daijirin Dictionary 3rd edition (大辞林 第三版 ) - "ときめく（ 動カ五［四］ ） : 喜びや期待などのために、胸がどきどきする。" = Due to the joy and the feeling of looking forward, the heart is pounding.
Daijisen Dictionary (大辞泉) - "ときめく［動カ五（四）］ : 喜びや期待などで胸がどきどきする。心が躍る。" = Because of the joy and the feeling of looking forward, the heart is pounding.
Looking forward is crucial in technology. Tools and frameworks are constantly evolving. Sometimes, this happens too fast, with people focusing too much on trends and buzzwords.
"Joy" is not the term I'd use for my experience with npm - quite often, it's exactly the opposite, I'm feeling very frustrated. But in going forward with my current project, npm is the tool that will let me reach my goals.
Yep, I agree that you have to look forward in tech, and evolve, but I think it's important to be rooted in the present and not to be swayed too much, or too far from the core of what you enjoy. Of course, sometimes you have to use a tool because of a work environment, or the high adoption rate in the industry. So, if you can choose, choose a work environment that uses your "happy" stack!
I have not had to use npm extensively, so I cant share your pain! The trend that some people hope for is to use native imports more in the future and reduce the reliance on npm, I believe that's the ecosystem Deno is going for
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.
Before answering that question, I'd go back to the roots of the KonMari method. "Sparking joy" is an imperfect translastion from Japanese, says redditor:
Looking forward is crucial in technology. Tools and frameworks are constantly evolving. Sometimes, this happens too fast, with people focusing too much on trends and buzzwords.
"Joy" is not the term I'd use for my experience with npm - quite often, it's exactly the opposite, I'm feeling very frustrated. But in going forward with my current project, npm is the tool that will let me reach my goals.
Yep, I agree that you have to look forward in tech, and evolve, but I think it's important to be rooted in the present and not to be swayed too much, or too far from the core of what you enjoy. Of course, sometimes you have to use a tool because of a work environment, or the high adoption rate in the industry. So, if you can choose, choose a work environment that uses your "happy" stack!
I have not had to use npm extensively, so I cant share your pain! The trend that some people hope for is to use native imports more in the future and reduce the reliance on npm, I believe that's the ecosystem Deno is going for