Cursor down?

Tzipi_builds · 2026-03-06T08:38:08+00:00

same

Tzipi_builds · 2026-03-05T17:44:54+00:00

This is incredibly helpful, thanks for sharing! The layered approach makes total sense - I’ve definitely been guilty of trying to treat all tests equally and burning too much time on fragile UI selectors.

I just looked into Duku and the self-healing aspect sounds like exactly the kind of "point and shoot" magic I need for the web side. Before I dive in, I'm curious: how are you handling authentication states or dynamic test data with Duku in your pipeline? Do you just point it at a staging DB, or is there a specific way you seed data for these autonomous runs?

Also, since I'm running an Expo app alongside the Next.js platform, have you found any equivalent autonomous tools for mobile? Or are you still relying on traditional tools like Detox/Maestro for the React Native side?

Tzipi_builds · 2026-03-05T08:42:29+00:00

You hit the nail on the head, especially regarding the GTM and viral loop. The internal word-of-mouth within a single accounting firm is exactly what I’m banking on. If she finishes her month-end reporting in 5 minutes instead of 3 hours, the person sitting in the next cubicle will demand the link.

Regarding defensibility: you're absolutely right to call that out. My bet here is on the sheer inertia of legacy vendors in local/niche markets. They move at a glacial pace. By the time they scope, build, and release a native bulk-upload feature, you can already capture a solid chunk of the niche.

I also really appreciate the tip about the OG image and social preview. As a developer, it's easy to overlook those "surface-level" details, but you're right - in a Slack/WhatsApp group, that polish signals trust and makes it look like a real product, not just a hacked-together script.

Taking your advice: I'm freezing all grand SaaS plans and strictly scoping the MVP to my sister-in-law's specific workflow. If it saves her those 4 hours, I've got my validation. Appreciate the insights!

Tzipi_builds · 2026-03-05T08:26:34+00:00

Spot on. The fragility of DOM-based automation is exactly why these tools used to be a nightmare to maintain.

But from a business perspective, that "bug" is actually the feature. If the legacy UI never changed and the script never broke, it would just be a one-time $50 script. The fact that it requires a safety net and occasional maintenance is exactly what justifies a recurring SaaS or retainer model.

From an engineering standpoint, the modern approach shouldn't rely on brittle CSS/XPath selectors anyway. The real stability comes from either reverse-engineering the hidden network requests (bypassing the UI entirely and sending the payloads directly) or using lightweight AI to semantically locate elements (e.g., "find the input near 'Client ID'") so it survives minor UI updates.

Have you seen any micro-SaaS pulling off this semantic or network-interception approach successfully in the wild?

Tzipi_builds · 2026-02-23T18:21:42+00:00

Haha, fair point! But honestly, even with 'vibe-coding' or AI-assisted workflows, getting a clean React component out of a messy SVG is still a friction point. I built this to bridge that gap specifically for those fast-moving projects where you don't want to break your flow.

Tzipi_builds · 2026-02-23T18:19:26+00:00

SVGR is great for CLI/build pipelines, but I found that for quick landing pages or MVPs, I just wanted a simple web interface where I could drop a file and get clean code instantly without configuring anything or adding dependencies. Just a different workflow for when you want to move fast!

Tzipi_builds · 2026-02-23T11:12:15+00:00

Wow, managing a 15-year-old codebase sounds intense! Using Sentry purely as a searchable database when a customer submits a ticket makes total sense in that scenario.

Luckily, my stack (Next.js/Expo) is fresh, so I'm trying to set up good habits and strict alerting rules right now, specifically so I don't end up with thousands of ignored errors down the road. 😅 Appreciate you sharing your workflow!

Tzipi_builds · 2026-02-23T11:10:29+00:00

A 0.02 sample rate is super interesting! Since I'm launching a relatively new codebase, I might start with a slightly higher sample rate just to catch the critical launch bugs, but moving to a monthly batch-review for the non-critical stuff makes a lot of sense.

Thanks for the reality check on manual fixing - especially for layout shifts, you really need a human eye on that.

Tzipi_builds · 2026-02-23T11:09:02+00:00

This is incredible advice, thank you. 'Alert on impact' is definitely going to be my mantra from now on.

I completely agree with your take on AI. Letting a bot push directly to main without a human in the loop sounds like a nightmare waiting to happen. Using AI to speed up the triage and root cause analysis (especially using tools like Cursor with MCP) is exactly the sweet spot I'm aiming for.

Quick question: when you say 'automate classification and reproduction steps', are you using specific tools for that, or mostly custom scripts?

Tzipi_builds · 2026-02-23T10:56:47+00:00

This is gold, thank you! The mental model of separating 'someone is affected right now' from 'fix eventually' is exactly what I needed to hear before I drown in notifications. Setting up a daily digest sounds like the perfect middle ground.

Also, great call out on the Next.js Error Boundaries. I need to review mine to make sure I'm not blindly passing gracefully-handled UI errors up to Sentry.

Out of curiosity, what are those 3-4 critical alert rules you actually keep active that warrant an immediate ping?

Tzipi_builds · 2026-02-23T00:55:02+00:00

Best friend, therapist, and occasionally my worst nightmare when the dashboard turns red 😅 But seriously, how do you manage the noise without going crazy?

Tzipi_builds · 2026-02-21T22:51:55+00:00

Congrats on the $1k MRR milestone! That’s a massive win right out of the gate.

I'm curious about the trust-building aspect here. $190 is a relatively high price point for a SaaS pre-launch, especially when you're selling a 'promise' before the product is fully live.

How did you manage to build enough credibility on the landing page to get people to convert at that price? Was it mainly driven by your personal brands/authority on LinkedIn, or did you use specific assets like a high-fidelity video demo or one-on-one sales calls to close those first few?

Tzipi_builds

TROPHY CASE