For anyone else on the fence about moving to CLI: I'm really glad I did.
I am converting a WordPress site to a much leaner custom one, including the functionality of all plugins and migrating all the data. I've put in about 20 hours or so and I'd be shocked if I have another 20 hours to go. What I have so far looks and operates better than the original (according to the owner). It's much faster and has more features.
The original site took more than 10 people to build, and many months to get up and running. I will have it up single-handedly inside of 1 month, and it will have much faster load times and many more features. The site makes enough money to fully support 2 families in the USA very well.
My Stack: Old school LAMP. PHPstorm locally. No frameworks. Vanilla JS.
Original process: webchat based since sonnet 3.5 came out, but I used Gemini a lot after 2.5 pro came out, but primarily sonnet.
- Use Claude projects for "features". Give it only the files strictly required to do the specific thing I'm working on.
- Have it read the files closely, "think hard" and make a plan
- Then write the code
- MINOR iteration if needed. Sometimes bounce it off of Gemini first.
- the trick was to "know when to stop" using the LLM and just get to coding.
- copy code into PHPStorm and edit/commit as needed
- repeat for every feature. (refresh the claude project each time).
Evolution: Finally take the CLI plunge: Claude Code
- Spin up a KVM: I'm not taking any chances.
- Run PHPStorm + CC in the KVM as a "contract developer"
- the "KVM developer" cannot push to main
- set up claude.md carefully
- carefully prompt it with structure, bounds, and instructions
- run into lots of quirks with lots of little "fixes"
-- too verbose
-- does not respect "my coding style"
-- poor adherence to claude.md instructions when over half way through context, etc
- Start looking into subagents. It feels like it's not really working?
- Instead: I break my site into logical "features"
-- Terminal Tab 1: "You may only work in X folder"
-- Terminal Tab 2: "You may only work in Y folder".
-- THIS WORKS WELL. I am finally in a "HOLY MOLLY, I am now unquestionably more productive territory!"
Codex model comes out
- I open another tab and try it
- I use it until I hit the "You've reached your limit. Wait 3 hour" message.
- I go back to Claude (Man is this SLOW! and Verbose!). Minor irritation.
- Go back to Codex until I hit my weekly limit
- Go back to Claude again. "Oh wow, Codex works SO MUCH BETTER for me".
- I actually haven't fussed with the AGENTS.md, nor do I give it a bunch of extra hand-holding. It just works really well by itself.
- Buy the OpenAI PRO plan and haven't looked back.
I haven't "coded" much since switching to Codex and couldn't be happier. I just say "Do this" and it does it. Then I say "Change this" and it does it. On the rare occasions it takes a wrong turn, I simply add a coding comment like "Create a new method that does X and use that instead" and we're right back on track.
We are 100% at a point where people can just "Tell the computer what you want in a web page, and it will work".
I'd heard Codex improved a ton since I last tried it (definitely prior to some of the latest improvements), and am really tempted to give it another shot. This is very much inspiring me to do so asap, thank you for sharing!
> > We are 100% at a point where people can just "Tell the computer what you want in a web page, and it will work"
> I await the good software. Where is the good software?
Exactly this, it looks great on the surface until you dig in to find it using BlinkMacSystemFont and absolute positioning because it can't handle a proper grid layout.
You argue with it and it adds !important everywhere because the concept of cascading style is too much for its context window.
I am converting a WordPress site to a much leaner custom one, including the functionality of all plugins and migrating all the data. I've put in about 20 hours or so and I'd be shocked if I have another 20 hours to go. What I have so far looks and operates better than the original (according to the owner). It's much faster and has more features.
The original site took more than 10 people to build, and many months to get up and running. I will have it up single-handedly inside of 1 month, and it will have much faster load times and many more features. The site makes enough money to fully support 2 families in the USA very well.
My Stack: Old school LAMP. PHPstorm locally. No frameworks. Vanilla JS.
Original process: webchat based since sonnet 3.5 came out, but I used Gemini a lot after 2.5 pro came out, but primarily sonnet.
- Use Claude projects for "features". Give it only the files strictly required to do the specific thing I'm working on. - Have it read the files closely, "think hard" and make a plan - Then write the code - MINOR iteration if needed. Sometimes bounce it off of Gemini first. - the trick was to "know when to stop" using the LLM and just get to coding. - copy code into PHPStorm and edit/commit as needed - repeat for every feature. (refresh the claude project each time).
Evolution: Finally take the CLI plunge: Claude Code - Spin up a KVM: I'm not taking any chances. - Run PHPStorm + CC in the KVM as a "contract developer" - the "KVM developer" cannot push to main - set up claude.md carefully - carefully prompt it with structure, bounds, and instructions
- run into lots of quirks with lots of little "fixes" -- too verbose -- does not respect "my coding style" -- poor adherence to claude.md instructions when over half way through context, etc - Start looking into subagents. It feels like it's not really working? - Instead: I break my site into logical "features" -- Terminal Tab 1: "You may only work in X folder" -- Terminal Tab 2: "You may only work in Y folder". -- THIS WORKS WELL. I am finally in a "HOLY MOLLY, I am now unquestionably more productive territory!"
Codex model comes out - I open another tab and try it - I use it until I hit the "You've reached your limit. Wait 3 hour" message. - I go back to Claude (Man is this SLOW! and Verbose!). Minor irritation. - Go back to Codex until I hit my weekly limit - Go back to Claude again. "Oh wow, Codex works SO MUCH BETTER for me". - I actually haven't fussed with the AGENTS.md, nor do I give it a bunch of extra hand-holding. It just works really well by itself. - Buy the OpenAI PRO plan and haven't looked back.
I haven't "coded" much since switching to Codex and couldn't be happier. I just say "Do this" and it does it. Then I say "Change this" and it does it. On the rare occasions it takes a wrong turn, I simply add a coding comment like "Create a new method that does X and use that instead" and we're right back on track.
We are 100% at a point where people can just "Tell the computer what you want in a web page, and it will work".
And I am SOOOO Excited to see what's next.