Chapter 2 of the code generators saga… The frustration phase. Almost rolling everything back. And I will DEFINITELY pay a good dev to review the code.
Continuing… fixing one thing and breaking another — common in the dev world — is a reality. Several of the times I managed to get out, it was because I knew how to read the code and ask about exactly the point that was breaking. Or ask it to be verbose in the console to see what was happening. By the way, that last one was one of the best things I learned for dealing with maintenance.
I STILL don’t see it as a reality. Lovable brings aesthetically good things, but now connecting it with Supabase has been… a challenge. Writing the policies… it gets them wrong a lot. Reloading in several places where it isn’t needed. And that’s while I’m still on basic CRUD. I want to see what happens when it’s time to connect the harder services that are in n8n.
I tried migrating to Cursor. Still struggling a lot with the IDE, and I really felt I was in an environment for devs. That’s not what I wanted. Back to Lovable we go…
Best things I’ve learned so far:
- Sending images of how you want it to look improves the result A LOT;
- Ask the way a product person would ask a team;
- Ask it to be very detailed in the logs so you can follow along in the console.
To be continued… :)
Originally written in Portuguese and published on LinkedIn on March 26, 2025. I translated it into English with the help of AI (Claude): it let me bring my LinkedIn posts to people who don’t read Portuguese without rewriting each one from scratch. I reviewed the translation to keep my original meaning and tone.