Post

I hate reviewing LLM PRs, just had one with similar user auth checks in middleware (with a 401), DI in the service (returning null), and as static calls in every action (throw new Exception). At least 3 checks of the user with every request. We already had user auth in a library.

Keith Henry@k17.dev

LLMs absolutely will not use any of JS's Set methods (intersection, union, difference, etc). They've been baseline for 2 years now. Every LLM insists on nested loops and will try to reset your code with them every chance it gets.

0 reposts1 like

They produce loads more code than they need to, most of it is crap, they never use what you already have, and cleaning them up often takes more time than writing the damn thing myself.