gbasin

you're doing what now?

me too except codex writes the code and i only look at git diffs :/

I don't believe that's true with 100% grass fed beef

I still use this regularly :) thanks for building it. any interest in open sourcing? i can help

I see, thanks. Seems just a matter of cost to reclaim it. Maybe regulation is needed

pardon my ignorance, in what was does it "consume water"? water cooling is closed loop

the main bottleneck will be model depth... you can only do so much with N layers, and recurrence has proven to be way less efficient (for now)

~210 calories

yep i switched to taza

i eat half a bar of it per day, amazing brain fuel

this was my main takeaway from 20th century philosophy lol

Yes I was specifically thinking of the latter with larger models, I think many many shot ICL still tends to outperform but you're right it's worth trying both for your use case

I am building in the mortgage origination space and have these sorts of enhancements on the drawing board... you hit the nail on the head that the bottleneck will be in QC and legal review, as 3rd-parties (especially regulators) may want to manually see the data you used to reach the conclusions you did. Although I'm still digging. You'd be interested in what we're creating btw, it's a crypto-based mechanism that enables instant digital mortgage origination, we should chat!