Andrea Saez

Me: I’ll just add a simple ICP builder

Also me, 48 commits later: what have I done 🫣🥳

It’s sleek, it’s awesome, it’s dangerously good.

I don't know who needs to hear this, but you are allowed to have ice cream for dinner.

I am very active and was approached by the existing team

In theory, keep things clean. Make sure there’s no self promotion, or shitty/unethical advise

Five rounds of “fix → refix → break → refix again” later…

The damn thing works. Elegantly, even.

Oh, and while I was at it:
🌙 Added dark mode
🧭 Improved onboarding
🧩 Connected more context between tools (the central intelligence system is coming to life)

Vibecoding, amirite

a man is crying while looking at a cellphone ALT: a man is crying while looking at a cellphone

Here’s what actually happened:
• I broke the entire backend
• Restoring Lovable only restored the frontend
• My brain tapped out somewhere around Round 3

I even considered reaching out to Elena Verna for help.

The goal was innocent enough:

“Just update the progress bar to show specific states.”

So this was a super fun weekend.

What started as a “quick onboarding tweak” turned into a 6-hour debugging odyssey through recursion hell, state management purgatory, and the occasional existential crisis.

Yes, I cried.

🤣

I probably won’t, but I can’t promise I won’t be tempted 🤣

Adding dark mode to any app is something I am never doing again.

What a special kind of hell.

Vibe coding dark mode is a f*cker

a man wearing a shirt that says the clash is screaming ALT: a man wearing a shirt that says the clash is screaming

I am now a mod on the product management subreddit.

That is all.

3 weeks and almost a paid user per week. Not bad.

#vibecoding

A good vibe coding prompt:

“Why do we keep having problems with x?” {whatever keeps breaking}

Ended up running a comprehensive test to let me know the fixes thus far had been patched barely holding things together, and ended up doing a completely refactoring

#vibecoding

The internet is down.

See you in the real world.

a man says well i was wrong in a blue shirt ALT: a man says well i was wrong in a blue shirt

Having to code HTML emails is a kind of hell I thought I’d never have to experience again.

Forma PM — Where ideas take shape Turn ideas thoughts into structured, exec-ready strategies. Forma PM helps PMs and PMMs build better product stories.

Cannot believe how quick and easy it was to build three new product pages, a new product, and a release notes page with @lovabledev.bsky.social

What could have previously taken me weeks took me three days

Check it out at www.getforma.co

a woman with long blonde hair and a lanyard around her neck ALT: a woman with long blonde hair and a lanyard around her neck

If you run a Slack community and are still using @here in the announcement channel….. a curse on all your houses

a man in a blue shirt is sitting in front of a sign that says #winning . ALT: a man in a blue shirt is sitting in front of a sign that says #winning .

Day 7 building Forma PM

Today’s lesson: get your SSO approved for production in Google.

Takes under 24 hours if you don’t have sensitive data scopes.

9️⃣ Speed isn’t everything

Speed only works when it’s paired with understanding. The more context you build in, the fewer things you break later.

8️⃣ Security debt is worse than code debt.

Code can be fixed. Trust takes longer to rebuild if SSO is constantly failing (its fixed now, I think 😅)

7️⃣ OAuth hides its failures well.

Credentials and setup can be right, yet timing or state handling still fails silently.

6️⃣ HTML emails are pure chaos.

Perfect in Gmail, broken in Apple Mail, unreadable in dark mode. Always test across devices.

5️⃣ UX and security rarely agree.

Validation emails make things more secure, but adds friction. SSO brought huge improvements, but a nightmare to set up.

4️⃣ Client logic causes trouble.

Anything involving access, limits, or payments belongs server-side where it’s consistent and protected.

3️⃣ Session management matters more than expected.

Keeping sessions valid across logins and refreshes can quietly break everything if you handle it wrong.

2️⃣ Security requires layers.

Rate limits, validation, and row-level policies each catch something the others miss. Ignore one and it will find you later.

1️⃣ Fast tools create faster problems.

Lovable, Supabase, and GPT make it easy to build, but they also surface issues earlier. Shipping quickly doesn’t remove complexity; it just moves it closer to you.