"Random" accidents that always go against you, too biased to be random.
But don't notice that too much, you might start to see patterns here and there that you're not allowed to, might get you banned from places, etc.
21–30 of 79 posts
"Random" accidents that always go against you, too biased to be random.
But don't notice that too much, you might start to see patterns here and there that you're not allowed to, might get you banned from places, etc.
Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight. Here are the docs: https://developers.openai.com/api/docs/guides/prompt-caching... The thread has little explanation as to what weird thing they’re doing to Codex that is making the default work poorly, and it kind of seems like it’s getting confused about whether it wants to set the caching mode or the breakpoi…
It’s really cool that we have this proof that US companies are half year behind Chinese models in architecture.
The fact that companies with access to SOTA non-public AI keep having these kinds of dumb bugs in something as simple as a chat app helps validate my disbelief of people claiming AI is ready to replace all software development.
The companies you see struggling are ripe for disruption.
I wonder if it's related to Codex wearing out SSDs.
The fact that companies with access to SOTA non-public AI keep having these kinds of dumb bugs in something as simple as a chat app helps validate my disbelief of people claiming AI is ready to replace all software development.
AI is ready to replace both jobs and companies. The companies you see struggling are ripe for disruption.
Funny how it is always more charges but never less or no charges. "Random" accidents that always go against you, too biased to be random. But don't notice that too much, you might start to see patterns here and there that you're not allowed to, might get you banned from places, etc.
Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight. Here are the docs: https://developers.openai.com/api/docs/guides/prompt-caching... The thread has little explanation as to what weird thing they’re doing to Codex that is making the default work poorly, and it kind of seems like it’s getting confused about whether it wants to set the caching mode or the breakpoi…
i dont know what the hell is going on lately i pop in to issues or discussions and its agents talking to each other or telling me what PR to merge I mean i use AI too but was taken back when an agent popped up dictating what i should do and so on....felt weird
It felt like they were trying to avoid me. They could have simply addressed me and given me the explanation they gave to the bot: it would have been simpler for him and more polite. I did in fact reply without waiting for the bot.
Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight. Here are the docs: https://developers.openai.com/api/docs/guides/prompt-caching... The thread has little explanation as to what weird thing they’re doing to Codex that is making the default work poorly, and it kind of seems like it’s getting confused about whether it wants to set the caching mode or the breakpoi…
It’s really cool that we have this proof that US companies are half year behind Chinese models in architecture.
Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight. Here are the docs: https://developers.openai.com/api/docs/guides/prompt-caching... The thread has little explanation as to what weird thing they’re doing to Codex that is making the default work poorly, and it kind of seems like it’s getting confused about whether it wants to set the caching mode or the breakpoi…
Slightly bummed out about it because in the past you could try different situations during a planning session and it wouldn’t pollute the cache but now it does. I’m not sure if forking the conversation has the same problem.