Press enter or click to view image in full size
My normal workday has gradually shifted toward the use of AI over the past year. It’s writing a good bit of code for me, but I see it as a performance enhancer, not a replacement for a competent developer.
Here’s a great example of how it helps me in real life: I recently wrote out some type definitions for GraphQL and then asked Codex to stub out the functions that would need to be called to fulfill those requests.
At first, it completely botched the entire request. It actually deleted the definitions I had written and then declared the work done. After some wrangling, I finally got it to do what I wanted. The entire thing probably saved me about 30 minutes over doing it manually — which isn’t nothing, but it’s not exactly a revolution, either.
A lot of my interactions with AI tools have been like this: definitely useful, but nothing groundbreaking.
The Codex CLI is a recent addition to my workflow. Before, I would copy code snippets into ChatGPT’s interface and ask it questions. It wasn’t really doing the work for me; it was acting like the good ol’ days when I would turn around to my cubemate and ask a quick question.
Using a CLI tool has obviously streamlined that, and it can handle complex tasks with relative ease. I’ve only trusted it on green…