BenMosher

I feel like the combo of arm + leg + back thrusters and an exoskeleton are sufficient to warrant the analogy.

It is 100% on the user to determine whether an article applies, or it's plain wrong.

You're not wrong, but isn't it especially difficult for an inexperienced person to judge whether an article applies?

This notion of "strangling" old code is new to me, but I think it is similar to a benefit I have seen with using Flux to manage SPA state:

You can always add more stores.

Since every store receives every dispatch, playing with a new way of managing state need not ever modify existing code; just create a new store and intercept the same actions with a different outcome.

On several occasions, I have even duplicated a store to try changing one or two things, leaving the original intact. This made me feel dirty at first, but it is actually a great way to try out new ideas without introducing any breaking changes, intentional or otherwise.

I'm trying out seeing how nature sounds improve my flow while programming. This one has some pretty impressive-looking hardware and good sound quality.

I like the idea of being able to listen to live, natural sounds. I have a suspicion that the open soundscape might lend itself to thinking clearly.

(that said, as I write this, there's clearly a plane flying over the unit streaming.)