153 karma · joined November 27, 2016
Second thing is you can starkly upgrade the token generation locally if you use agent teams. Single conversations are memory bandwidth bound and don't fully make use of your compute. If you can batch tokens from multiple agents you can easily 5x token generation.
So yes the generel meaning applies to test setup and running and also to the agent cli which is the harness for the model.
And if you combine the graphs for solar and wind from this: https://aleasoft.com/european-solar-and-wind-energy-producti...
You can nicely see that they are complementary in terms of energy production.
I have been thinking about this in terms of a data oriented programming language like clojure, but having types/schemas. If you use Union Types for something like getting a value out of a map for a specific key, then if you knew the schema of a specific map you could reduce the return type from {T, Error} to just the type of the value T that you know is there.
Basically a sufficiently smart compiler with the necessary information could make you not have to deal with errors at all in certain cases. With Result/Option/Maybe this would not be possible. It would always infect the entire callstack and you would always have to deal with it.
For example. The US would consume its entirety of pumped hydro storage in a third of a day.