You cannot introspect model training by prompting the model. Whatever answer it hallucinated on your query "where do you know that from" has almost certainly very low bearing on reality.
Personally I've found the opposite useful - I mostly use OAI models with OMP harness and I have a rule instructing it to summarize if any work was omitted or if it made any surprising changes. Sometimes the agent will forget to do some piece of work or invent a new bizarre way of doing things, but quite often it is able to self reflect on this at the end of the session.
The new GUI is... not great. But the UX old UI was downright awful. There were like 5 different paradigms how to use individual screens, not just layouts, completely different ways to navigate and interact with controls.
After couple tens of hours you memorized the arcane keyboard invocations to do what you wanted, but it never felt intuitive.
You get matched with an expert in 30s to 3min, which then starts a back and forth with the AI agent and the expert which goes on for 10 to 60mins till the AI is happy.
This works well for many tasks, but for others a more async mechanism where the expert doesn't feel rushed might be better.
My understanding is that most OpenAI users are on a free tier. Secondary effect of this is that OpenAI free tier model capability (assuming Luna) is what what most users associate with frontier AI capability giving somewhat warped view to many people.
The main issue with worktrees is that you can't have the same branch opened in multiple worktrees which makes many things harder than the ought to be. I don't really understand why we need that limitation, otherwise the tooling is good enough.
JJ workspaces don't have that limitation. They do limit you to not having the same working copy commit opened in more than one location, but that's not particularly restrictive with JJ since you're probably squashing changes from the working copy into a permanent commit anyway.
The roping of an unbroken horse or untrained bull is illegal.
In Australia at least three people have been injured by bulls in past two months (man suffered serious injuries after being gored by a bull at Mortlake livestock exchange / woman suffered significant leg and pelvic injuries following an incident with a bull on a private property at Crediton in Mackay / etc.)
Even at the time, the example was almost certainly more representative of the concept than meant to be a specific thing that happened all the time. Then as now, people have animals; animals sometimes do bad things; when is the owner responsible?
There are certain cats that are aggressive about expanding their territory; they'll break into other houses and attack the cats there. (Had this happen to us -- cat came in through a cat-flap a few times, until something happened that scared enough that it never came back.) The first time your cat does that sort of thing, you can say "I had no idea, it's not my fault." But if your cat has a habit of doing that, and you still let it out at night, you're no longer blameless.
If all of these meshes use the same shader (which they do, its just PBR) they can be all drawn with a single multidraw indirect call.
Edit: thinking more about it, since the objects are small they could be rendered with mesh shaders achieving further perf improvements. Also fine grained decomposition helps with culling. IMO the real problem is that rendering in game engines does not map well to modern hardware. Unreal engine went full software rendering with nanite replacing the whole pipeline (which brings significant drawbacks) and everyone else is using graphics with techniques 15 years out of date which leads to this mismatch between what is possible with hardware and what is good practice with game engines.
There are several tiers to these services, some are selling real us phone number verifications at about 0.5usd/text while others are selling virtual phone number verifications at much cheaper. From some limited experience with the former, there is rarely if ever any problems with rejections.
reply