jmalicki
Answers are proofs, not numbers, and there is a ton of nuance, and it is incredibly hard to grade.
It's not as easy as judging the quality of a computer program written as an assignment.
And that's a critique of the original article... that the broader "S&P 493" isn't showing gains might be for the reasons you describe.
It was not on a level that nudges GDP growth for a long time. The irony is that maybe the productivity didn't increase until book publishing plummeted, since enabling a lack of physical books was a huge productivity win.
This isn't a debate about whether industries improved. When you look at GDP, do you see an uptick in GDP or not?
The original quote was often seen as a paradox. At least one major interpretation of the original quote is that "the computer revolution is so obviously helping the economy, that if it doesn't show up in GDP, is it even a meaningful measurement, and how can we fix that?"
But it is very fitting to discuss that quote - the original article discusses multifactor productivity, the same relevant measurement, and earnings of the S&P 493. There are two ways to interpret it - is AI not increasing productivity, or are we not measuring productivity, and is there "dark matter" somewhere in the economy that is not being properly measured?
That's one of the "everywheres" the author of the statement was talking about, which is the point - you could see every part of the economy seemingly improved, but it did not show up at the macroeconomic measurement level.
It was until the 2000s that computers caused an uptick in measured productivity at the GDP level, though.
If companies can better understand their customers so they can give me products that better fit my needs, or inform me of products I couldn't have known about otherwise, that's a win for everyone.
Luckily the first, and increasingly the second, are being replaced by Slack!
OpenAI never even gets the data, those orgs get to host OAI's model as local within their datacenters, OAI never touches it - you still have to trust Google, MS, Amazon, but I would trust any of them before OAI directly.
Whenever I see my main agent do a compaction, that to me is a clear sign I didn't have it delegate bounded tasks enough.
The longer your chat gets, the slower and more expensive it gets.
Subagents are expensive but they scale way closer to O(n) than O(n^2).
Have some agents make bug reports/feature requests/roadmaps (linear is very AI friendly), others coordinate, others work on grinding out an individual ticket.
If there is a good ticket-level description, it's a waste of time IMO to have a main agent do it, that should be an agent with fresh context that will do it better faster (the shorter the context, the better models are at using the context they're given).
There is a fixed cost (and some maintenance) to e.g. fine tuning ModernBERT.
Maybe once you include all of that it might be a half-day to a day of engineering time to set everything up in a maintainable fashion.
For Jev, it takes all of 30 seconds of prompting. And it's not that much more expensive to deploy vs. a BERT model.
If the proof isn't trivially translatable to lean, is it actually a good proof?
The migration will just fail with no harm done.
There have been tons of applications for this. People were using earlier LLMs like BERT for classifiers long before LLMs became viable chatbots.
That is very not true for many cases. Agents generating code are usually painfully slow, finding workflows that replace that reasoning with running code usually speed things up in my experience.
You can pay for higher cache time, you can pay for NVMe KV cache for an hour that can just be reloaded, etc., at a lesser tier you can pay for the KV cache to be stored on a network store (I guess I'm unclear if that last tier would be cheaper than recomputation, not even 100% sure of the NVMe with direct GPU<->storage DMA) depending on your model settings.
If a program runs slower when you give it more RAM, the problem isn't giving more RAM.