Tips on avoiding going down long rabbit holes with nocode platforms that can't solve hard problems?
I am seeing this with Lovable, Verdent, Replit: I am clear, RAG my prompts, clean them with Claude Opus 4.6, find that with tough problems, they'll tell me something is fixed or done, and it isn't. Not even close. And I'm burning costly credits, making no progress.
I'd love to learn what others are doing.
I'm building a multi-agent tool that integrates with 25+ LCNC sites and also IDEs, and yes, there are tough problems with the tool's awareness of what a user is doing in a console or fields in a browser window. I'd apprecaite it if the nocode platform simplay told me, "no can do," rather than trying one thing after another, staying stuck, and costling me $100 or more per day to keep failing.
Thanks, in advance, for your suggestions!
21 views


Replies
vibecoder.date
Code is just a specification that a computer executes, that is all, The higher level you go the more it starts resembling plain english.
I avoid no code tools, developer background aside, in the age of AI it's a lot easier to write a specification of the outcomes you want, and then work with the model on how to achieve them.
RiteKit Company Logo API
@build_with_aj thanks for that - always the best way, of course.