237 karma · joined October 21, 2019
From what I've been gathering, this split in success seems to depend a lot on the types of tasks, the domains / programming languages / frameworks used, and style of prompting.
I couldn't get 5.2 to follow instructions for the life of me, even when repeating multiple times to do / not do something. 5.3-codex was an improvement and 5.4 while _usually_ decent still regularly forgets, goes on unnecessary tangents, or otherwise repeatedly stops just to ask for continuation.
Sure, I'm paying 3x more per request, but I'm also doing 5x fewer requests.
Or well, used to. Still bummed about them dropping 4.6.
QUIC getting hardware acceleration should close this gap, and keep all the benefits. But a kernel (software) implementation is basically necessary before it can be properly hardware-accelerated in future hardware (is my current understanding)
Like yes, for a bunch of structures you can neatly automate it (see most rocket production), but the shapes of (current) cars don't easily offer themselves to similar options. Automation is possible but would probably be finicky and require a lot of space and energy (for the heating).
but someone else please jump in if you know better/more.
> obtain customer PII (Personal Identifiable Information) associated with outstanding balances for Framework purchases.
I don't have outstanding balances (I'm aware of) for like two years now. Something doesn't quite add up. They may just have sent this email to previous customers too for good measure, but I'd love to know more about that.
hilarious
It progressively introduces new game mechanics, which you automate away when they start being annoying.
Also: At this point I probably spent about the same time building excel sheets for figuring out prioritization of upgrades as actually playing the game.