Readit NewsI really appreciate this point from mitchellh. Giving thoughtful constructive feedback to help a junior developer improve is a gift. Yet it would be a waste of time if the PR submitter is just going to pass it to an AI without learning from it.
Is there a struggle when using Ash between the "Phoenix Way" (gen.auth, scopes) and eg AshAuthentication? Ecto vs Ash.Query?
Afaik NHTSA tracks safety-related defects and recalls but they don't publish "failure rates". It would be nice if they did.
One can't escape psychology, one thing no school taught me (and they should have since we all deal with this in some way! plus its not that complex). Once I grokked the basics, dealing and with people and understanding them became much easier.
What about people who are deeply passionate about their mission and chose to devote their life to it?
Internet, text messages, etc are roughly that: the direct costs are so cheap.
That’s not the case with LLM’s at this moment. There are significant direct costs to each long-running agent.
Tests poke and prod with a stick at the SUT, and the SUT's behaviour is observed. The truth lives in the code, the documentation, and, unfortunately, in the heads of the dev team. I think this distinction is quite important, because this question:
> Do we have a bug? Or do we have a bad test?
cannot be answered by looking at the test + the implementation. The spec or people have to be consulted when in doubt.
Is it "System Under Test"? (That's Claude.ai's guess)
(I've certainly seen it done though, with predicable result.)
In my anecdotal case: I behave like the former in some cases (crafting) and the latter in others (travel planning)
I wouldn't say one way is always better than the other.