wrcwill

doesn't look like it, looking at the motocross photo (0:19 in the "Structure your prompts for better results" video)

this reads as a very low quality and probably fully llm written post.

the analysis is very suspicious: “gpt 5 mini had api failures due to wrong temp setting”? wtf?

whatever you used to slop your benchmark didt even take the time to set the temp to 1 (which the docs say is required)

ugh this is so amateurish. i swear since the release of o3 this has been happening on and off.

can someone explain why zig is often compared to rust?

i understand zig as a better C, but in what world is another memory unsafe language a good idea?

i mean i kinda get if the thing you are writing would require LOTS of unsafe, then zig provides better ergonomics

however most programs can definitely be written without unsafe and in that case i dont get why wed do this to ourselves in 2025

why not take advantage of memory safe, and data race safety?

Unless I'm missing something, this has nothing to do with asynchronous code. The delete is just synchronous code running, same as if we called a function/closure right there.

This is just about syntax sugar hiding function calls.

can you ctrl-f now?

still a low frequency pwm phone.. what i would give for a modern no-pwm / high frequency pwm phone

i split the context and give it in two messages :/

definitely 1!

it seems to truncate your prompt even under the "maximum message length" and yeah around 55k is where it starts to happen.

extremely annoying. o1 pro worked up until 115k or so. both o3 and gpt5 have the issue. (it happens on all models for me not just the pro variations)

with the new 400k context length in api i would expect atleast 128k message lengths and maybe 200k context in chat.

how are you using it? codex-cli?

well no, thats where it gets confused. as soon as you sail across to the other pole you are forced to go up to a speed of 1670kmh.

when models try to be smart/creative they attempt to switch poles like that. in my example it even says that the max speed will be only a few km/h (since their strategy is to chill at the poles and then sail from north to south pole very slowly)

--

GPT-5 pro does get it right though! it even says this:

"Do not try to swap hemispheres to ride both polar summers. You’d have to cross the equator while staying in daylight, which momentarily forces a westward component near the equatorial rotation speed (~1668 km/h)—a much higher peak speed than the 663 km/h plan."

while it doesn't take away from the article, i find it worrying that it seems mostly written with chatgpt

"This is not just a technical glitch; it’s a deep theoretical problem that suggests we don’t really understand the beginning at all."

"The bounce is not only possible – it’s inevitable under the right conditions."

ugh