Загрузка видео...

Не удалось загрузить видео

На главную

Boop explains why he thinks Epic is testing a new 30 ping minimum comp feature: - Former Epic employee confirms having worked on it - They didn't disclose what they were testing this eval cup - Everyone who is playing the Eval is 30 Ping - NA Only

165,582 просмотров • 5 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

your eval measured one system. production ran another. they start from the same idea and end somewhere else, which is why the number was right and the outcome was not. the code is the same until someone rewrites it for prod, because the eval lived in a notebook and prod is a service. then the data diverges. clean fixtures in the test, late and incomplete data in the run. then execution diverges. the eval assumed every call lands. production has retries, timeouts and rate limits. by the end the two runs share a name and nothing else. > why nobody catches it both sides are internally correct. the eval measured what it ran. production ran what it was given. neither one is wrong, and neither one is responsible for checking they were the same artifact. so the gap widens quietly. someone patches prod without touching the eval. someone adds a fixture without touching prod. no test anywhere fails. > what to actually do ship one artifact. the code that was measured is the code that runs. model the friction. whatever the real environment charges you, charge it in the eval too. easiest way to see the gap on your own idea, without writing the harness: (only first 100 registrated) it runs the tested code live, unchanged. that is the whole point. and treat the eval as a prior, not a result. it tells you what to expect. only the live run tells you what happened. your eval was accurate. it was accurate about something you never shipped.

Hanako

45,239 просмотров • 2 месяцев назад