$85,000 in tokens later: What I learned from scaling agentic coding at Lovable
1–10 of 61 posts
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#2I am not the author but Lovable tells me I'm in the top 10% of users. It's a great tool. Not affiliated in any way.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#3> Reviewing AI-written code line-by-line isn't practical or a good use of anyone's time. And the usual answer to problems created by the use of AI is to use more AI, so you switch to AI reviews by default.
Ugh. Sure, for non-critical stuff that might be acceptable, but for anyone working on core banking or infrastructure PLEASE don't be doing this.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#4> Reviewing AI-written code line-by-line isn't practical or a good use of anyone's time. And the usual answer to problems created by the use of AI is to use more AI, so you switch to AI reviews by default. Ugh. Sure, for non-critical stuff that might be acceptable, but for anyone working on core banking or infrastructure PLEASE don't be doing this.
It depends I imagine. Core bankend bank system, database, transactions and such sure, but what about the web and mobile client? I'm down to get better customer experience if they can ship faster without breaking the bank.
What about fraud detection and prevention? I hope to think I'm not alone in that perspective that it's acceptable in those cases.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#5[dead]
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#6> Reviewing AI-written code line-by-line isn't practical or a good use of anyone's time. And the usual answer to problems created by the use of AI is to use more AI, so you switch to AI reviews by default. Ugh. Sure, for non-critical stuff that might be acceptable, but for anyone working on core banking or infrastructure PLEASE don't be doing this.
It depends I imagine. Core bankend bank system, database, transactions and such sure, but what about the web and mobile client? I'm down to get better customer experience if they can ship faster without breaking the bank. What about fraud detection and prevention? I hope to think I'm not alone in that perspective that it's acceptable in those cases.
Its fine for web and mobile as long as you can't get sued if data leaks or you get hacked.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#7> Reviewing AI-written code line-by-line isn't practical or a good use of anyone's time. And the usual answer to problems created by the use of AI is to use more AI, so you switch to AI reviews by default. Ugh. Sure, for non-critical stuff that might be acceptable, but for anyone working on core banking or infrastructure PLEASE don't be doing this.
It depends I imagine. Core bankend bank system, database, transactions and such sure, but what about the web and mobile client? I'm down to get better customer experience if they can ship faster without breaking the bank. What about fraud detection and prevention? I hope to think I'm not alone in that perspective that it's acceptable in those cases.
> What about fraud detection and prevention?
It's easy to see both pros and cons of that. I guess, like most stuff, it depends upon the appetite for risk vs the downsides of false positives/negatives and incorrect analysis.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#8Instead of employing an engineer for a year we burned an obscene amount of resources to generate code which will enable vibe coders to burn more resources.
But we’re lovable! Cute smile. Heart emoji.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#9> Reviewing AI-written code line-by-line isn't practical or a good use of anyone's time. And the usual answer to problems created by the use of AI is to use more AI, so you switch to AI reviews by default. Ugh. Sure, for non-critical stuff that might be acceptable, but for anyone working on core banking or infrastructure PLEASE don't be doing this.
It depends I imagine. Core bankend bank system, database, transactions and such sure, but what about the web and mobile client? I'm down to get better customer experience if they can ship faster without breaking the bank. What about fraud detection and prevention? I hope to think I'm not alone in that perspective that it's acceptable in those cases.
Fraud detection and prevention have been using AI to determine things long before ChatGPT came on the scene. Of course, they call it machine learning, but it's all linear algebra under the hood. Just that ChatGPT has a really big hood.
Re: $85,000 in tokens later: What I learned from scaling agentic coding at Lovable
#10Earlier quoted context omitted.
It depends I imagine. Core bankend bank system, database, transactions and such sure, but what about the web and mobile client? I'm down to get better customer experience if they can ship faster without breaking the bank. What about fraud detection and prevention? I hope to think I'm not alone in that perspective that it's acceptable in those cases.
Its fine for web and mobile as long as you can't get sued if data leaks or you get hacked.
Fortunately AI lawyers are much cheaper than real lawyers.