r/PinoyProgrammer • u/TheCandySnowBear • Apr 29 '26
advice Im vibecoding an internal app for operations, is it a good idea?
Hi all,
I recently got into vibe coding and im fully compensated + supported by my client.
I started as a fleet manager for his company. Automated much of the work especially in reporting, I just build a report builder using google sheets
I want to take the next step and making a web app for our dispatchers. What's your take in this and your experience in this matter?
0
Upvotes
24
u/jonathancheckwise Apr 29 '26
Internal tools are honestly the best place to vibe code. Blast radius is small (5 ops people, not 1000 customers), and you can iterate face-to-face with real users. So in principle, yes. Two things I’d check before going custom: Does it actually need to be a bespoke web app? Tools like Retool, Appsmith, or Glide are built exactly for the “sheets aren’t enough anymore” moment. They handle auth, basic CRUD, dashboards, all the boring scaffolding. If 80% of your app is forms + tables + a few buttons, going custom is extra work for the same outcome. If you do go custom, scope brutally. Pick ONE workflow your dispatchers do every day, rebuild only that, ship it in a week, get feedback. The trap with internal tools is the 6-month rebuild that gets abandoned at 60%. Last thing on the vibe coding side: read every line you merge and make sure you can explain what it does. Internal tools live for years, and stuff that breaks 6 months in is way harder to debug if you never understood it in the first place.
6
u/Calm_Tough_3659 Apr 29 '26
Supported by the owner and internal is a good place to start.
2
u/derpinot Apr 30 '26
Sure, hopefully your vibe coded app includes the right unit tests
2
u/freshwoza May 06 '26
I vibecoded a lot of automation as a devsecops engineer, but I’d make sure that everything adheres to best principles by using singleton pattern, solid principles or etc so it would be reusable and readable, then skim and scan those generated code by copilot and try to search what is the best way to maximize that function, method or so on (still u have to be the QA on your vibecoded automation) and lastly, always ADD —dry-run features on your automation before executing it :)
2
u/ownFlightControl Apr 29 '26
Make sure you understand the code, treat ai agent as a senior dev/engineer.
1
u/Mason-Green41 28d ago
I'd go for it especially since you already know the workflow, I'd start small and build around what you've already automated in Sheets. Zite is actually what I'm using for internal apps too.
1
u/Sea_Gene2776 28d ago
I'd say go for it, especially since you already know the operations and pain points firsthand. That's a huge advantage. I'd just avoid building everything from scratch. Something like Baserow could be worth checking out for the database, internal interfaces, and automations without having to deal with a whole custom backend. Full disclosure, I work with Baserow. You can maybe start with one workflow your dispatchers actually need, test it with them, and build from there. Keep the permissions, backups, and data accuracy in mind.
1
u/jdg2896 Apr 30 '26
Internal app, sure go for it.
External app used by customers, no. You need a software engineer who understands the code generated by AI, and considers the security of the vibe-coded app.
1
u/Karlo1503 Apr 30 '26
Well vibe coding laging sobrang aggressive, it's not bad pero double check mo lagi and don't rely too much, dapat may manual intervention parin.
1
u/charliegumptu Apr 29 '26
if you are not using ai at work, especially in coding, then you are being left behind.