Next up is experimenting with implementing tests. Sometimes when refactoring a component, Codex will forget to add back an element that was there before. Think a timestamp in the article card for example. I think I can steer it not to forget if it has to check against tests.

Codex is also really good at browsing files, you don't need to attach context manually nearly as much as with Cursor.

If you had a bad GTP-5 experience in Cursor so far, me too and this doesn't compare. I think Cursor might have optimization techniques that make the model way inferior as in Codex.

* Ask Codex for a first refactor to make sure it follows React best practices, break the file in a few components and lib/util files.
* Prompt away to add features.

Some pro tips:
* Start in ChatGPT, it's good for a quick prototype with UI. Ask for the code to be in a Canvas to have live preview.
* When you're happy with a first draft, open your VSCode, scaffold a new vite/ts/swc project, add Tailwind, and your file. Make sure it runs, Codex can help.

It was able to integrate multiple features from the same small prompt, fix UI/UX, but also come with its own UI/UX suggestions. Very impressive.

Also whatever you do don't take people for idiots. The cooking demo was clearly preplanned and the AI was on a script and I think this is the part that failed. Don't blame it on the WiFi.

Show you've been using the glasses as a teleprompter! Control the slides and lights in the room with the wristband! Control a drone! Some super spy shit!

Gentle reminder that this is in the App Store's requirements 🙂