this post was submitted on 27 Nov 2025
127 points (90.4% liked)
Technology
77090 readers
3819 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
For sure, I am talking about smaller projects where programming elements are relatively low key and critical parts are the business logic and how it impacts UX/UI and use case flows.
I was between projects and I needed money so I accepted a project from a repeat client where I knew 80% of it very well (and how to implement it), but there were parts that I vibe coded (albeit they were simple enough that I could understand the logic of what I was deploying even though I don't know how to code).
The contract size was simply too small for me to get a subcontractor, I would be giving them most of payment (while doing 80% of the work).
I think it's fair to use vibe coding in such situations.
I would not risk vibe coding in a situation where I felt I would be undermining the clients' project (I want repeat clients and I don't want to have to spend time fixing things for free).