Auth is hard

Somehow, I burned multiple hours on setting up basic Google authentication using auth0 as the provider,

I intend to use auth0 for the blogs just because it's low-effort. For the application stack, we actually need to stick with supabase because of how much it connects with everything else including authorization matters.

One thing I learned is that AI can't easilly handle SDK changes. When something moves from an older version to a newer version, ambiguity becomes a factor. This is the main reason why I'm dropping Remix in my tech stacks.

Amibuity kills AI development

In the past, We've used Remix V2 for the campaign dashboard in the election. It worked fine! But the problem with it is that the lead engineers are planning to build Remix 3, and they're going to be a framework with their own design libraries and everything. They want to redo react.

This means that the probability of AI using the wrong things goes way up.

Some worries.

Time is ticking, and I'm killing too much time on small things. I need to finish setting up supabase for local development, and trying to make it work on a production cluster as well.