joshuaavalon

The difference between JWT and session is where the state is stored.

For session, you need a centralized backend to access the data stored in the session. For JWT, you only need to verify the signature of the token to trust the data stored in JWT.

JWT solves the problem of having multiple separated service that need to share data.

Things do break in production does not mean you don't take any measures to reduce the chance of happenings.

Following your logic, why should we test our code before deployment?

Everyone should push to master and deploy to production. Things will break anyway even if we tested our code.

Most of the services provide backup codes when you enable 2FA.

I don't think that's a huge problem.

GitHub issues have labels. You can add "Resolved", "Won’t Resolve", "Paused" as you like.

Many large repositories use labels to show the state of the issue. You do not need to rely on open or closed.

There is a setting in URL of the password called "Match Detection"[1]. You can change it to "Host" if don't want it to match subdomain.

[1]: https://bitwarden.com/help/article/uri-match-detection/#matc...

I heard MKBHD said it only alert you alert you went home or workplace. Otherwise, it will keep alerting everyone on public transport.

If you want central authority, isn't it the job of CI?

Use CI to verify the commits fits the styles and review the commits before merging.

The problem for me is other people not using it. When I call another library, there is no type hint and the documentation is poor.

You can only read the code and guess the type yourself.