Corey Knowles

Yeah.

For example, right.

Or maybe if there's an on-call skill, there could be a century on-call skill.

And that one actually produces like an output, um, that, uh,

you know, lists everything by engineer and like sends an email, right?

So yeah, at least that's how we're thinking about it right now.

This is maybe taking one step back, but the way that I would think about making Codex successful, I don't actually have anything written down for this, but we could just... That's okay.

So the first step is just install it in your favorite tool.

So it could be your IDE or your terminal.

So that's step one.

Right.

Then step two is just test it.

Like you don't need to overthink it.

And then I think from there you want to configure.

And the way that I think about configuration is you want to do first, you want to set up what I would call the inner dev loop.

And there's the outer dev loop.

And then there's like automation.

So the inner dev loop is basically like, does Codex know where you keep your context?

Does it know how you like to write code?

And you should just test it, because it probably will just infer your style, but there might be things about your style that are hard to infer.