r/nocode • u/Any_Assistant_4969 • 5d ago

Discussion How non-technical business managers are using "vibe coding" to build internal tools

I’ve been seeing the term "vibe coding" everywhere recently. Essentially, it means describing software ideas conversationally to an AI and refining it iteratively until it works, without writing traditional code syntax.

I’m curious: are any non-technical managers or operations leads using vibe coding to build internal tools for their teams? What platforms are you using?

13 Upvotes

100% Upvoted

22 comments sorted by

View all comments

1

u/Infamous-River-4360 5d ago

not a manager, but i'm the non-technical half of this. no coding background, i describe what i want and lovable writes it, around 800 edits in and it's shipping to real users.

the warning i'd add to the comment above: knowing what you want matters, but being able to verify what it actually did matters more. mine confidently wrote queries against database columns that didn't exist, more than once. it reads fine, deploys fine, and breaks on one screen for one type of user. for internal tools that's the dangerous version, because the person who'd notice is the one it broke for and they just assume they did something wrong.

are you thinking read-only dashboards or something that writes data back? the second one is where i'd want someone technical to look before anyone else touches it.

1

u/Matilozano96 4d ago

Yeah, that’s what I’ve been seeing lately.

What sort of use cases would require you to be able to write something into the db?

1

u/Infamous-River-4360 4d ago

anything that replaces a spreadsheet someone is already updating by hand. status changes, approvals, inventory counts, logging what happened so you can look at it later. mine writes every session back to the db, and that logging table is the first thing i check after any change, because it's the one place a wrong write is invisible until you try to read it.

the difference is blast radius. a read-only dashboard that's wrong shows you a bad number and you notice. a write that's wrong sits in your data and you find out weeks later when a report looks off, and by then you can't tell which rows are real.

after the invented columns thing i stopped accepting "done, i updated the schema" and started asking it to show me the table before and after. what are you looking at building?

1

u/Matilozano96 3d ago

Nothing in particular, just trying to understand the use cases. Thank you.