> there's not enough specifics in your wall of text to help me point out what's going on in any useful detail, though.
Sorry, wasn't sure what was most valuable to people reading this. Some examples:
1. It feels like getting quality code (which our team cares about alot) is hard to get out of LLMs if it's not just piping data around or copying an example I explicitly point to. It doesn't get the scale to build with - often it does weirdly generic code that's not really relevant, or wants to write alot of boilerplate that's not useful (e.g. spamming tests).
2. It hallucinates documentation often enough I've gone back to hunting for source documentation myself (e.g. AWS details).
3. It will flag false positives on junior-engineer "problems" when I request a code review (if there's data being mutated in two different places with different conditions, chances are it'll not understand it the first time).
4. It'll get stuck on nonsense (the "thinking" output makes me cringe) and try to go in random directions if I ask it to debug a problem. I don't think I've had it actually find the actual problem once (but it has found a couple other unrelated problems which is nice).
5. In Plan/Build mode, it'll not follow a plan. It also seems to oddly dodge writing secure code for auth-related stuff (if I hadn't have read through OAuth myself, I wouldn't have caught it).
> tried to streamline processes and then got yelled at by CS, sales enablement, and marketing.
Yes haha! And a few other departments besides.
Anyways thanks for your time :)