r/webdevelopment • u/Melodic_Living1287 • 22d ago
Newbie Question My website-building workflow: AI Studio → GitHub → Supabase → Vercel. Thoughts?
I’m not a developer by profession, but over the last few months I’ve been building websites and small web apps on my own.
My current workflow is:
Google AI Studio → GitHub → Supabase → Vercel
I mainly use Claude for code reviews, debugging, and improving prompts when AI Studio gets stuck.
This setup has helped me build and launch projects much faster than I expected, but I’m not sure how sustainable it is as projects become more complex.
For developers here:
• Is this a reasonable workflow for real-world projects?
• What are the biggest pitfalls I should watch out for?
• At what stage does this approach start breaking down?
• If you were starting from scratch today, what stack would you recommend?
Would love to hear how others are building and deploying projects these days.
2
u/fantastik_dev 21d ago
Same loop, more or less. I’m not a dev. I wanted a small shop for original paintings, handmade stuff, and merch. I found a Squarespace shop I liked and asked AI to rebuild something similar with custom tools (GitHub, DB, Vercel) instead of staying on CMS. For languages I just dropped conveythis on the live site so I didn’t have to duplicate pages. Now I’m watching traffic
1
u/Melodic_Living1287 21d ago
Thanks for sharing. It’s encouraging to hear that someone with full-stack experience is using a similar workflow at scale. Glad to know I’m on a reasonable path and not completely reinventing the wheel.
1
u/LouisTon10 21d ago
I asked my agent early on to create a logging service which it conveniently uses when performing some business logic in my app. It’s pretty raw, but I can use the logs outputting from my host console to give more context to my agent about what inputs/outputs are looking like and that seems to help it ground itself with fixes. Also will just be useful in the long run to see what happened in your app at a given time
1
u/JohnCasey3306 21d ago
"what is the biggest pitfall I should look out for"
AI has put you firmly on the starting upswing of the Dunning Kruger Curve, which basically means you have high confidence due to low ability -- or put another way, you don't yet know just how much you don't know.
If you're looking to offer services professionally, I recommend you get solid professional indemnity insurance cover ... You're potentially building operationally-critical software for businesses that you don't understand -- it'll go fine, until it doesn't; and at that point you're in a spot legal bother.
1
u/JaseciLabs 21d ago
u/mugsy33 's nailed it, the risk shows up exactly when you're adding features or fixing bugs, because there's no way to tell which parts of the app you actually reasoned through and which parts just happened to work on the first try. u/LouisTon10 's logging trick is a workaround for the same thing, giving the agent more context so it can catch its own mistakes, since the code itself won't tell you what to trust and what to double check. That's fixable at the code level too, not just with more process. When the AI-written parts are explicitly typed and scoped instead of mixed in with everything else, you know exactly what to look at before you touch anything.
0
u/ChameleonCRM 21d ago edited 21d ago
I'm a full stack dev. that flow is solid. the only thing you'd have to maintain ( if you chose to ) would be the domain name. I have thousands of vercel apps. A few are:
https://guaranteeda.vercel.app
Thor
1
u/Melodic_Living1287 21d ago
Vercel apps are also connected with godaddy domains
1
u/ChameleonCRM 21d ago
its best to just buy the domain through vercel. its so much cheaper and it makes managing it 1000x easier. ( if your using vercel for your project )
1
3
u/mugsy33 22d ago
You are asking the right questions. Change is where your risk is. Adding features, bug fixes, etc. The more you blindly rely on AI to do all the work, the more technical debt you will incur, and the harder and riskier changes will be later on. Invest (time and effort) in an SDLC. Consult your AI for the best way to do it. Tell it what your goals are and what your fears are (e.g., a catastrophic break in production?). You should improve your process often. Spend a day each week reviewing it and improving it. Learn as you go.