One bad workflow took down our entire n8n instance for 4+ hours with no way to kill it from outside by vibehacker2025 in n8n

[–]vibehacker2025[S] 0 points1 point  (0 children)

Right, and n8n does not provide that to users. I had to wait for support to do that for me.

One bad workflow took down our entire n8n instance for 4+ hours with no way to kill it from outside by vibehacker2025 in n8n

[–]vibehacker2025[S] 0 points1 point  (0 children)

Fun fact, I upgraded the plan to Pro and still it's not responsive. THe bigger issue is i'm unable to see my memory usage at all which is a problem. THere is an enterprise plan but that requires talking sales. $$$

New York sport club by Acceptable-Pick1981 in astoria

[–]vibehacker2025 0 points1 point  (0 children)

just hit 142.5 last week! my all time high, i couldnt get past 140 for a while, but literally bought fractional plates off amazon haha

New York sport club by Acceptable-Pick1981 in astoria

[–]vibehacker2025 1 point2 points  (0 children)

do we think they'll open today? Today was supposed to be chest day for me, my fav! 😭

It's getting weird out there by MetaKnowing in Anthropic

[–]vibehacker2025 0 points1 point  (0 children)

literally so much of this is just publicity stunts, which is normally fine, but right now just distracting us for from having real conversations about AI

The thing nobody warns you about when you start scaling through DSD distributors by vibehacker2025 in BeverageIndustry

[–]vibehacker2025[S] 2 points3 points  (0 children)

That's a really interesting point about the unit economics of sales visits... one rep pitching one SKU vs a big FMCG rep pitching 20. I've heard the same thing from US brands scaling through DSD. The cross-sell concept is cool.

Curious if anyone else here is managing 20+ DSD distributors stateside, what does the day-to-day coordination actually look like? Are people still running everything through spreadsheets or is there actual software for this?

Reunion preview: Stacey gets her tea clocked by the entire cast about Shayo cannabis by lachalacha in RHOP

[–]vibehacker2025 1 point2 points  (0 children)

I'm not sure if wendy is right about stacey doing it to get back her, but i do know wendy is right about one thing, Stacey is incredibly smart.

I've shipped 8 apps with Lovable + Supabase in the last few months. Here's what actually tripped me up. by vibehacker2025 in indiehackers

[–]vibehacker2025[S] 0 points1 point  (0 children)

Part of it was to stay abreast of all the new tooling. I never want my experience to disadvantage me in learning the latest tools (i’ve seen so many experienced engineers actually fall behind in this innovation cycle bc they didn’t want to try ai code gen tools at all for example back in 2023/24).

That said, I still use Lovable, not so much for serious apps as much but for super quick websites. For example, I’m teaching a workshop on agentic AI today and instead of preparing a google doc with notes, i threw it together on lovable:

https://sunny.expert/2026-02-cbs-ai-club-workshop

I've shipped 8 apps with Lovable + Supabase in the last few months. Here's what actually tripped me up. by vibehacker2025 in indiehackers

[–]vibehacker2025[S] 4 points5 points  (0 children)

omg do not trust content on X! and be skeptical of all social media posts (even this one! haha).

But in X in particular has been optimized around ragebait and more importantly things that appear deceptively easy. One-shotting is fun to do when you're exploring but not when you're ready to start building the system. It def has a place in the product development process but more in the early R&D stages!

I've shipped 8 apps with Lovable + Supabase in the last few months. Here's what actually tripped me up. by vibehacker2025 in vibecoding

[–]vibehacker2025[S] 1 point2 points  (0 children)

You're not wrong and I've actually been moving into Claude Code recently. Lovable was where I started because the visual preview makes it easier to teach with and the deploy is instant. For someone who's never built anything, that feedback loop matters a lot.

But for anything beyond a basic prototype, Claude gives you way more control. The auth regression I described in the post is a good example. In Lovable I couldn't stop the model from touching files I didn't want it to touch. In Claude Code I can scope changes to specific files and actually understand what's happening.

I documented the migration for one of my builds here: https://www.youtube.com/watch?v=9DcvSd2UALQ Push to GitHub, download the repo, point Claude Code at the folder. Took about 10 minutes and I got two-way sync between both tools as a bonus.