That's not how this works. Assume less about my level of expertise. By the end of a session, I understand the internals of what I'm implementing. What is shortened is the search space and research/prototyping intervals.

If I didn't ultimately understand where I was going, projects like this hit a dead end very quickly, as mentioned in my caveats. These models are not yet ready for large-scale or mission-critical projects.

But I have a set of a constraints and a design document and as long as these things are satisfied, the language will work exactly as intended for my use case.

Not using a frontier model to code today is like having a pretty smart person around you who is pretty good at coding and has a staggering breadth and depth of knowledge, but never consulting them due to some insecurity about your own ability to evaluate the code they produce.

If you have ever been responsible for the work of other engineers, this should already be a developed skill.

Are you making a DSL then? That would make more sense.