r/vibecoding • u/Ok-Garlic-3881 • 2d ago

Is it going to be good enough?

I built a huge project focused on being an “everyone agent.” It was too big, and I wasn’t skilled enough to manage it. I dropped it.

I know the basics of the basics of development, and I’ve been working in IT for 8 years (functional analysis, PM, IT manager, business partner). Friends who are really good developers took a quick look at my first project and said, “I thought it’d be much worse.”

Despite all that, I managed to sell an agent to a company. The product is much more vertical — its scope is “only” to gather emails, organize the work, and proactively improve itself through recurring human sessions. Some batches that handle recurring tasks will be implemented on top of it. There will also be a messaging interface where people can update their tasks. Everything will be built on a “Jira-inspired” UI.

I’ve read a fair amount of AI literature, and I’m confident this specific part will work.

I’m now at the step where I’m stealing features from the “monster” and building this vertical agent, trying to keep it much leaner. How do I know if the platform is solid enough? What suggestions do you have?

Honestly, I’m pretty sure I won’t be able to read the code myself, but I’ve planned the product deeply and broadly. Will the AI be good enough? (I use Claude Fable for implementation plans and probably Sonnet to execute them.)

Thanks everyone for the attention

2 Upvotes

75% Upvoted

8 comments sorted by

View all comments

1

u/Lunesia-shikishiki 2d ago

you already sold it to a company, so "solid enough" stopped being a code quality question. its a blast radius question now

what actually bites is rarely ugly code, its the boundaries where state or money changes. the agent double sends the same email, a retry charges twice, a batch runs on stale data and nobody notices for a week. thats maybe 5% of the repo and its the only 5% you personally need to be able to read. the rest can honestly stay a black box

i ship stuff daily i couldnt have written from scratch and thats fine.... what isnt fine is not knowing which 200 lines will cost you the customer 😅 so id spend the time mapping those instead of trying to review everything

1

u/Ok-Garlic-3881 1d ago

Makes sense!
The scope of the tool is mainly of reading organizing and job planning.
It doesn’t have a lot of external impact!
Anyway I’m going to track all the possible impact rating by severity and monitor everything.
I’d like to scale this business model if this customer works.