1,361 karma · joined August 28, 2012
If the data centers do get built and come on line, we will see an increase in compute supply and that should lower inference prices.
If they don't, for whatever reason including financial ones, then we will not have enough compute to meet demand and inference prices will rise. But this would mean the financial concerns were misplaced.
Where is the equilibrium point?
I’ll be re-watching The Inner Light in his honor tonight.
I have also found that replying STOP = sign of life, your number is marked as “someone alive on the other end” and gets resold to 20 new lists.
However, lately, I have had several experiences that have completely changed my mind - the here is a high level goal (involving gathering production logs, setting up an eval, running tests, iterating, including diagnosis and coming up with new ideas, etc. and don’t bother me until it’s done. The experience has been incredible.
This has been possible because the agent has a way to iterate and hillclimb against a metric it can measure. Relatively easy in the world of software.
I’m now convinced that we will unlock the same gains once make other domains similarly “iterable”.
Eg Agent comes up with 100 new proteins, runs in lab autonomously, gathers results, iterates. One month (or whatever) later, you have your new protein designed.
The point is that it boils down to writing the tests correctly, regardless of who is implementing the actual code. Hand-written code without test coverage has the same problems as AI generated code.
These days, I tend to start my coding sessions by the high level problem I'm trying to solve vs the prescriptive, specific solution I may have in mind. It often surfaces ideas and approaches that I did not know about.
There could still be more unknowns that I did not encounter and by definition don't know about.
And the final output could be wrong, wording, exact legal terminology etc.
Can we say working with an actual lawyer is guaranteed to be better, more correct? Lawyers are people and they also make mistakes, wake up on the wrong side of the bed, hate their job etc, just like the rest of us.
I had start with asking for a contact with some details I provided. But then I ask the model to be an experienced corporate lawyer and ask me a series of questions to gather the details it needed and then write the contract. The result covered a lot of details that were highly relevant but were absent from the original attempt.
The key insight is that you can lean on the model to cover your unknown unknowns.
It is possible to reduce token usage. It’s just much harder than the basic approach.
Separately, I've been wondering how uneven human progress is. I think we have come a long way in electronics (relays to vacuum tubes to transistor to … to an M5 chip) but in some other domains, like moving objects through space, we are basically mostly reliant on thrust generated by burning fuel (EV's are a genuine advance, but mostly due to battery tech).
Don’t take this as an argument against these technologies. It’s a huge win to not be increasing the CO2 concentration in the atmosphere by burning fossil fuels.
I have found that sometimes a smaller model with max reasoning is actually more expensive than using the next tier model with a lower reasoning effort. It’s certainly faster.
But for writing, I usually see the advice that says you should read a lot instead of write a lot. What gives?
OTel looks like something designed by a committee of committees, funded by someone who is in the business of selling cloud storage/data warehousing services.
An example iirc was waiting for luggage at the airport. It takes min of x minutes for the first bags to show. In one version, passengers went directly from the gate to the luggage carousel and waited x mins for the first bag → unhappy. Then the airport decided to add a long, round-about "walk" path from the gate to the luggage area that burned some of those minutes → same total "wait" but happier passengers.