Case in point, I have a Rust project with a target/ directory with about 10GB. Compile times from scratch takes about 10 minutes. (I do not love this)
With this mobile app I need to upload the code to the cloud, right? Or does OpenAI expects me to compile huge projects on my phone?
So basically, it is like you are typing on your terminal on your computer from your phone.
(The refactor's been to support Jujutsu VCS.)
You must be kidding me.
A key point is that after the "vibe" session you presumably also have a lot of tests written. So they can easily refactoring the code afterwards if there are major aspects you don't like when you get back to your desktop.
How do you think the world has worked for the past thirty years? AI has just caught up with human skill is all.
https://x.com/karpathy/status/1886192184808149383
Forgetting code exists is by definition not suitable for serious work. However, OP said in the following paragraph, that this would be a first draft, and that the code would actually be reviewed and tested properly before being integrated.
At which point it is by definition no longer vibe coding, because you do care about the code! It's just an AI assisted workflow, but now we call all of those vibe coding for some reason. (Naming things is hard!)
If vibe coding means not caring about the code, then a literal translation of the term would be "not caring about coding" coding.
This is just like everyone who says, “An iPad is not suitable for serious work.”
By which they (and you) generally mean, “What I do is serious work. What you do is unserious work.”
I think I do serious work – I mean they pay me for it? And I have only copy/pasted and just run whatever code’s been generated by AI for the past 12 months or so. Whenever I can I just let the AI run it itself.
Sad to learn that I’ve been so unserious all this time.
> Naming things is hard!
Indeed.
Imagine saying that you don't need to look at the roads or have no hands on the wheel whilst driving because someone-else said that the car can 'drive' itself; therefore, no need for anyone (including taxi drivers) to learn how to drive.
Just because a machine can generate plausible looking code does not mean you don't need to look at it or not know how it works or why it doesn't work.
I'm also completely fine if it gives me hold mustic while it's working.
Would make my walks much more productive.
I unsubscribed from Claude after the performance regressions around the time of the Opus 4.7 update made it unusable. Been using Codex since then, and I've definitely missed being able to make these drafts. So I'm looking forward to trying this out.
Wouldn't you be doing the exact same thing had you been sitting at your computer when you had the idea?
Perhaps the person who wrote that had the mindset of "when I am away from my work, I want to be disconnected and present with the world around me, this updates now makes it so that I now have an excuse to carry work with me"
Maybe they're in a toxic/abusive work relationship where taking breaks is already difficult and this might lead to justifying working from your phone as "expected"
My question to you is: what is wrong with moving a little slower? Is time to prompt an optimization of a real bottleneck?
At least, that's how I code through my phone. But it does require some forethought in establishing your automated workflows. I'm at the point where my entire dev system has established templates for CI/CD so I can preview work in staging and production is still a manual step (obviously).
I have Claude Code with access to Azure environment (via CLI) where app components are deployed and also to the code base repo. I paste an error message or explain the symptom. CC works through various configuration checks and network tests etc across the Azure resource list and also the application logic and surfaces the root cause of the error precisely. Easily 1-2 days of effort if I had done all those myself (this is an inherited code base) -- would have had to learn a few of those skills along the way or may not have thought about some of the checks if i were on my own -- all done in about 45 mins with basic human-in-the-loop guidance.
Of course learning it the hard way would have meant deeper understanding and first-hand exprience for me. But there is no guarantee I wouldnt have given up mid way frustrated or other priorities prevented me from pursuing this in full.
Process (all on my phone)
* Create new repo on github
* Tell Chatgpt the project and ask for a readme and agents file
* Manual upload the files to github
* Go to Codex and tell it to review the code and carry out steps in readme
* Connect project to Vercel
* If needed, create a DB
* Ask ChatGPT for the schema and run the sql
I have done this kind of work for years and now I can create things like this on the way back from a meeting. It's broken my business model by the way.
Here is one of the apps, for mental health - pretty much all done on my phone.
https://you-are-ok.vercel.app/
So having Codex in app removes one little barrier and I will take that.
Actions were not working on the android app. Known issue for a long time
https://community.openai.com/t/gpts-custom-api-calls-not-wor...
I did the same solution described above - Bookmarked the custom GPT, added to home screen and would run it in browser.
It seems to be working now. So I can start building out custom GPTs, share with my clients and not have a big training piece to onboard them.
Edit: https://chatgpt.com/g/g-697edc35e2888191a331217cd0483a67-men...
Take a pic of a menu and create a group meal/degustation for your budget.
Once you've used these coding agents a lot, you develop a pretty intuitive feel for how they work, what they're capable of, what they're good at, and where their weaknesses are. Hopefully, you're already pretty familiar with the code base you're working on. Combining the two, this means you can get quite far essentially "vibe coding" (i.e. not looking at the actual code) on a new branch.
So if you have some idea or some issue you want to fix on the go, you just iterate with the agent for a bit (presumably no more than a couple hours) until the agent outputs an implementation. Here, I do claim there is some "skill" (which is a function of your codebase familiarity, general SWE ability, and facility with AI agents), and if you're good, this implementation will be halfway decent a high percentage of the time. Then when you're back at your desktop, you can review the changes carefully/do some proper testing/debugging etc. But you've saved a good chunk of time- an initial draft is already waiting for you.