I assumed they meant using the LLM to extract the citations and then use external tooling to lookup and grab the original paper, at least verifying that it exists, has relevant title, summary and that the authors are correctly cited.
2,179 karma · joined April 12, 2007
(2) the subculture of the compulsive programmer, whose ethics prescribe that one silly idea and a month of frantic coding should suffice to make him a life-long millionaire. --ewd1036
a pure function doesn't change its inputs, it simply uses them to craft it's outputs.
bringing in an object or function via parameter to perform these side effects still leaves the function impure.
valve is certainly not rent-seeking. it offers service that is valuable to users, and take care of online infrastructure for games published through it, indefinitely, at no running cost to the developer.
As one of many, many examples, a galapagos turtle reaches sexual maturity at 20 to 25 years of age, and lives 100 to 200 years.
it was a sin that python's type system was initially released as a nominal type system. they should have been the target from day one.
being unable to just say "this takes anything that you can call .hello() and .world() on" was ridiculous, as that was part of the ethos of the dynamically typed python ecosystem. typechecking was generally frowned upon, with the idea that you should accept anything that fit the shape the receiving code required. it allowed you to trivially create resource wrappers and change behaviors by providing alternate objects to existing mechanisms. if you wanted to provide a fake file that read from memory instead of an actual file, it was simple and correct.
the lack of protocols made hell of these patterns for years.
They simply need choose which negative stories they print, which opinions they run. How do you frame misrepresentation vs a differing point of view? How do you call out mere emphasis on which true stories are run. Truths are still truths, right?
It's not infrequent today to see political opinions washed through language to provide reasonable deniability by those using it.
Hell, it's not infrequent to see racism, bigotry and hate wrapped up to avoid the key phrases of yesteryear, instead smuggling their foulness through carefully considered phrases, used specifically to shield those repeating them from being called out.
'No no no. Of course it doesn't mean _that_, you're imagining things and making false accusations.'
The government should be the government, and corporations should be corporations. Nothing good will come of having them bleed together.
Like church and state, you keep them separate for the good of both.
creating them server-side risks having a network error cause a client to have requested a resource be created without receiving its id due to a network error before receiving the response, risking double submissions and generally bad recovery options from the UI.
if you need users to provide uuids for consistent network operations, you can have an endpoint responsible for generating signed uuids that expire after a short interval, thereby controlling uuid-time drift (must be used within 1-5 minutes, perhaps), ensuring the client can't forge them to mess with your backend, and still provide a nice and stable client-side-uuid system.
for the uuidv47 thing, you would apply their XOR trick prior to sending the UUID to the user. you presumably just reverse the XOR trick to get the UUIDv7 back from the UUIDv4 you passed them.
To be crude but accurate, we're looking at semantic drift from a jerk being a jerk off to a jerk ass.
all integers have a square, while not all integers are prime.
in any given span, you'll see more primes than squares, however.
more dense?
for the rest of the net, ROBOTS.TXT is still often used for limiting the blast radius of search engines and bot crawl-delays and other "we know you're going to download this, please respect these provisions" type situations, as a sort of gentlemen's agreement. the site operator won't blackhole your net-ranges if you abide their terms. that's a reasonably useful thing to have.
the article, if you should choose to read it, is explaining that people have the misconception you appear to be having due to the 'let it fail' catchphrase. it goes into detail about this system, when failing is appropriate, and when trying to work around errors is appropriate.
as erlang uses greenthreads, restarting a thread for a user API is effectively instant and free.
this, too, mentions Yeager as the initial developer, and that CISCO licensed and enhanced his work from Stanford.