Thanks

https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines

Nice photos, you should take more :)

I've never used Auth0 and I've never heard of FusionAuth :) Okay, it's not entirely true that I've never used Auth0, I skimmed over the docs... but the main idea of my article is that no matter which service or 3rd party plugins you use if an outage can happen it will happen eventually.

We usually work with "2 + 1" or "3 + 1" week sprints. Where that "+ 1" week is for retrospective and maintenance work, where we usually upgrade all packages to their latest version and fix any eventual bugs. It keeps front-end development much saner.

A one-liner if you use yarn: yarn upgrade-interactive --latest

This is the best illustration I could find

Sayed Alesawy Replace it with a regular struct which accepts the dependency on it. If it gets complex you can write a factory method on the struct.

Andrey Panin http://misko.hevery.com/code-reviewers-guide/flaw-brittle-global-state-singletons/

Singletons are horrible advice, don't follow that pattern. Anything that creates a static, package level variable is bad.