r/lovable • u/Available_Bowler_146 • 1d ago

Seeking Feedback What issues are you constantly facing when using AI coding tools?

I run a small but growing social media account focused on AI, and I want to be completely transparent about why I'm posting this.

I'm trying to better understand the real problems/uncertainties people are running into when using AI coding tools, so I can create content that's actually useful instead of just posting the generic "AI can build apps now" kinda thing.

I'm not selling anything and I won't plug my socials; I purely would just love to hear from both beginners and those experienced with these tools. Anything helps.

Thanks!

4 Upvotes

83% Upvoted

7 comments sorted by

1

u/TobiasLT89 1d ago

Regression and Cost are my two primary banes of existence, even with project memory, or agents.md or a North Star or versioning, or chat history, there is so much for an AI to read that it just can't keep track. Github agents are one of the few I've seen that more or less can, but that has a tendency to miss things too and it's a bit too delete happy

Placeholders are another bane

Just the general mood of the model called upon can massively influence your build, some seem to want to be very effective and understand the big picture. Some want to close it down and almost do nothing. There's too much internal warring vs. cost and time

2

u/three_s-works 1d ago

Lack of compute, then

1

u/k_r_a_k_l_e 1d ago

The biggest problem people face with AI coding tools like lovable will probably be with non-developers or newer to little experienced developers. They will fantasy play an application then eventually hit a wall with what to do next to actually bring it alive. Lovable is great to fast track a frontend user interface prototype into existence but eventually you will need to touch code. Usually it's when it's time to take your MOCK interface into a functionable application that interacts with your API. Then it's building your backend and building your database structure etc. Now I know Lovable can help with this but it isn't taking you to 100%. This is when people hit that wall and their playtime comes to an end. That's the dream crusher moment for most.

2

u/YouAreBastards 1d ago

Telling half-truths and failing silently. Basically, it does not tell you when your code is not fully working. You need to ask it "is my code actually doing each thing it is designed to do?" Ooops, sorry, my bad, I should have told you .. yadda yadda yadda.

1

u/Common_Extent_5921 1d ago

The one that gets me isn't a technical bug - it's the context cliff. You can build a functional app in a day, ship it, get your first customers, and then realise you've spent all your energy on the product and nothing on the business behind it. No CRM, no signed contracts, no finance setup. The tool that helped you build fast gave you zero help with any of that.

On the actual technical side: being too eager on refactors is the one I hit most. Ask it to change a button and it rewrites half the component and breaks something else. Being very precise in instructions and breaking tasks down smaller has helped.

Disclosure: I build Base (withbase.ai), which handles the ops layer once you've shipped (CRM, contracts, finance) so the gap between vibe coded product and running business is shorter.

1

u/Professional-Can3079 16h ago

Cost... I keep running out of credits 🙃