HN user
I can't take the argument seriously when they ask "Pop quiz: You’re going to get hit by something coming at you at 50 miles per hour; given equal mass, would you rather that be a small object, or a large object?"
Either way you're dead.
Well, Chekov is not Scotty
And both Charles Keating (actor) and Charles Keating (Lincoln Savings & Loan) passed away in 2014 :-)
It's possible that Adams was expanding on an Alan Kay quote "Technology is anything that wasn’t around when you were born"
Depth of use over the lifetime of an app is a quality all its own that often not appreciated. A recurring pattern at $dayjob is that a new manager or director will join a business unit and declare an existing app as the worst terrible, no good, horrible app they've seen and they're going to fix that. A year and a half later the new app is finally delivered with 80% of the original functionality and a fresh set of bugs. The new dev team sees the surface functionality but misses a lot of the hard earned nuance the old system accrued over time. This is a pattern that existed long before LLMs.
Now add a retention policy of 30 days. Business memory lived in those emails and now it's 50 First Dates
someone vibed a production push
In a similar vein: https://www.youtube.com/@christopherhelmke
It's running his Signal chats.
You didn't get the invite???
A question we all have to ask ourselves. What would I trade for efficiency?
Is that you Molesworth???
And still fatal
https://www.ctvnews.ca/vancouver/article/pedestrian-dead-aft...
In this case it was a bicycle and not an ebike. That said, anecdotally, many ebikes I see regularly travel faster than the people powered versions
The Amanda solution is the intuitively obvious to even the casual reader. The Einstein solution is quite succinct but takes years to understand all the nuance in the one liner. :-)
I appreciate both for different reasons.
Pretty much bang on. I do have to remind myself that discipline in commit messages helps future me.
Admittedly only gave a quick skim but essentially looks like Deutsch-Schorr-Waite.
Thanks for the chuckle - you know there's more than one marketing guy out there who will say in all seriousness "I can do that for you" :-)
I checked in with Scribble as he did the typesetting. He apologizes for the error but says working without opposable thumbs makes the work more challenging.
Not to be confused with the protocol :-)
Say it aint so. I learned all about lasers from Britney.
Let's not forget the Salmon Arm salute :-)
The authors concoct a Rube Goldberg legal framework on the assumption that an AI agent is acting as an independent legal entity. A straightforward way would be to say that any AI agent is acting on behalf of someone and that someone is who shall be held accountable.
It give me the concrete basis for "being the computer" that I put to use a year or two later programming assembler on a PDP-8I
:-)
"You still can't print a high-tolerance metal part at scale and cost-effectively..."
Dan Gelbart has a response (with caveats)
From the early 1800's, created by a single person.
It seems my hypocrisy knows no bounds
He had any number of great lines but this one I really enjoyed.
Yes, you are correct. Nondeterministic grammars are not linear but quadratic. In the case of your palindrome example (thanks btw, added to my grimoire of grammars) I believe the quadratic is: (3n^2 + 6n)/4 (I wish HN did MathJax)
I need to do a bit more digging in to the distinction between ambiguous and nondeterministic.
When implementing parsers I enjoy the directness afforded by an Earley parser. No rejigging the grammar to suit LL, LR etc. No gotcha's with PEGs choice operator, etc.
Most grammars I end up using for practical applications are linear - so far, quadratic has been a spectre from afar. :-)
Use an Earley parser. A properly implemented Earley parser will do unambiguous grammars with left/right/mutual recursion in linear time. The worst case ambiguous I've worked with is UBDA (Earley, 1970). UBDA produces the equivalent of all the permutations of a binary tree - which is Catalan(n). If you generate all the combinations as you parse it won't complete before the heat death of the universe for fairly short strings.
More than once I've found myself going down this 'little maze of twisty passages, all alike'. At some point I stop, collect up the chain of prompts in the conversation, and curate them into a net new prompt that should be a bit better. Usually I make better progress - at least for a while.
Interesting - _q4 on a pair of 12Gb 3060s it runs at 20 tok/sec. _q8 (25Gb) on same is about 4 tok/sec.