vaishnavsm

Amidst all the slop videos nowadays, I find this format oddly refreshing.

I feel like there's a fundamental shift in the user interface that's causing this. People are starting to expect an "agentic interface" - that they are able to give kinda vague inputs and nudge things to work in a way they like, over the traditional experience of having increased clarity at the cost of increased setup (drag and drop, many UI first interfaces, etc).

I was editing a google doc yesterday and found it annoying that i had to find the "link" option from the context menu instead of just saying "turn links into links" and moving on.

This imo impacts everyone, regardless of how developer-ey you are. Perhaps non-devs expect a "friendlier"/more "agentic" interface now? Don't have the right vocabulary to explain.

I really want to love KeyCloak. I've had really bad experiences with weird uptime bugs and crash loops that kept me from giving it an honest retry over the last couple years.

It also really shows its age, imo. The interface is clunky, roles and groups having overlapping responsibilities is confusing, making custom UIs for it makes me feel ancient, etc.

I really can't complain though. There is simply no alternative that's as open atm. It's also not easy to make one ( I tried :( ).

Keycloak and Better Auth aren't as fundamentally different as you may think! Better auth supports authn/z, being an identity _source_, being an identity provider, being an OIDC/SSO provider (so others can login using better auth), rbac, SAML/SCIM, and a ton more. It's actually really powerful! Most folks found better auth as an alternative to next-auth/auth.js - but better auth does a lot more than those.

(some of those features are enterprise only)

ECS really isn't scalable. imo a multi-account EKS cluster is a bare minimum. It's what I use for my todo list app, and it works great!

This seems to be focused on Python, but for all the TS devs out there, what you'll see will be implicit `any` errors. Quick word of warning on having LLMs fix those - they love to use explicit `any`s or perform `as any` casts. This makes the lint error disappear, but keeps the actual logic bug in the code.

Even if you ask it not to use any at all, it'll cast the type to `unknown` and "narrow" it by performing checks. The problem is that this may be syntactically correct but completely meaningless, since it'll narrow it down to a type that doesn't exist.

The biggest problem here is that all of these are valid code patterns, but LLMs tend to abuse them more than using it correctly.

There's an easy shortcut in the second level past the climb on the pink pipe and before you climb the ramp where you can jump to the semi-circle on the lower platform on the other side. Love it!

Looks like the scheduled maintenance led to unexpected downtime?