🧭 THIS WEEK AT BuildProven
Howdy, it’s a short one this week. I’d like to do a bit of recap of I guess 6 months or so using AI and coding with Claude Code and Codex.
🧰 Worth Your Click
Here are a few things I found recently:
Claude Code creator shares some advanced tips
Ryan Carson’s OpenClaw setup - Start with this but I am tweaking it further - all I can say is getting agents working is really difficult!
AI & Economy - interesting article showing how much economics needs to advance due to AI
Claude Computer Use and Dispatch - Have Claude control your computer and kick off tasks from your phone - I use dispatch and it’s pretty cool, saves a lot of hassle setting up SSH to your Mac etc.
Claude Code can kick off reviews with OpenAI codex! Definitely good. I have found codex is WAY better at code reviews.
HBR article, managers vs executives views on AI - a divide!
🗺️ FEATURED INSIGHT
A semi random list of thoughts and hints about coding with AI:
Some IDE tools exist like Cursor and Replit and Windsurf - I think for super fast, absolute beginner starting, Replit is great. I’d recommend using that and learning what is possible.
Beyond Replit, next best is to subscribe to either OpenAI codex or Anthropic Claude Code. Small $20 monthly cost but the things you can create are amazing.
Interestingly, I’ve been subscribed to Claude Code for the last 6 mths or so. However, Codex seems to be more and more robust as I use it more. It seems to ‘somehow’ produce better code. It definitely does far better code reviews. So, strange that I am finding it better, even though the benchmarks show Claude Code slightly ahead.
Start out curious and just have the tool help you -
I have an idea for tool or app or website or mobile app XYZ - how could I go about building that, what is the best, simplest approach to building that. Create a best approach and plan.Some handy hints for building with AI -
- break it up into steps - ask the AI for the steps
- execute each step, test it and test continually - tell AI to write the tests!
- if you don't have an engineering background, just ask for best practices - ask how to create quality product, how to test, how to specify what you want
- build the step, test it, confirm OK and move to next step
- try not to go too fast - the technology is amazing and you can start to think to build things in parallel, start multiple tasks etc etc - that is the dark side! not quite, but it's complex and leave that for later.
Building is one thing. Deploying is another.
- creating something on your local computer is great and cool.
- sharing that is another thing.
- generally, you'll need to 'deploy' whatever you've built - so it has an address on the internet that people can use
- as always, ask your AI tool of choice! --> 'how can I deploy this'
My recommendation: vercel!!In summary:
grab a subscription to Claude Code or Codex
think of some ideas and simply ask and chat with AI how to build such a ‘thing’
build in steps and test, test, test —> more rigorous approaches in future newsletters
when satisfied and mostly working/MVP [minimal viable product] —> chat how to deploy/release
Weekly build logs from a 25-year program manager who codes with AI.
— Brett
👉 Hit “Reply” and share your experience — I read every one!