Mumps
Joined 8 years ago
Joined 8 years ago
Do people not feel like LLM speak (Claudisms) is infecting their own diction? Saying 'a new "shape" of LLM' sits so very poorly.
A LLM never has and, in their current architecture, never can/could experience suffering or real change of state.
The general and expected case for humans is that capacity. A human my indeed lose capacity, e.g. being braindead and in severe cases we do indeed say that they are not conscious or able to suffer (different argument: some would of course say that is suffering in and of itself)
+1.0mm vote to adding metric please!
It is clear, specific, and terse. It keeps both llm tokens down and human prose-reading to a minimum.
Christ in pijamas. TLAs should be a capitol offence. Even worse so, somehow, when undefined.
"Thanks. I have access to ChatGPT as well. But I ask people for help when it fails. Your thoughts are smarter than GPT's, please provide those, next time."
Though, I'd like to be more succinct/terse.
> Directions we think are wide open ... Curriculum learning
BabyLM and offshoot published a pretty convincing body of work on exactly that (which suggests it's not particularly relevant to LM training).
As I read your page, I really felt like the brevity-thoroughness tradeoff went the wrong way.
Move to DST and if you want the ability to start your day later and end later, [...].
Your comment about p<0.05, feels out of place to me. The p-values here are << 0.05. Like waaaaay lower.
Perhaps Fisher's exact is more appropriate, on the per-word basis?
Like OP, I've been similarly struggling to get as much value from CC (grok et c) as "everyone" else seems to be.
I'm quite curious about the workflow around the spec you link. To me, it looks like quite an extensive amount of work/writing. Comparable or greater than the coding work, by amount, even. Basically trading writing code files for writing .md files. 150 chat sessions is also nothing to sneeze at.
Would you say that the spec work was significantly faster (pure time) than coding up the project would have been? Or perhaps a less taxing cognitive input?
Zero-shot is indeed very cool. And it's super useful/useful for the developer masses that don't know, care, or work pressures don't allow, for proper evaluation and calibration.
But it would be good that we don't over-hype these things.