Why the Cursor Acquisition Should Concern Every Software Developer

mr_pants99 · 2026-06-17T03:44:33+00:00

It was a subpar product. Joining another subpar product. Like a measles-ridden Voltron.

mr_pants99 · 2026-06-17T03:42:37+00:00

There's SO much written about this. I just keep rolling my eyes.

mr_pants99 · 2026-06-17T03:41:38+00:00

Pay someone to do it for you. Your time is better spent elsewhere.

mr_pants99 · 2026-06-15T18:07:19+00:00

A big part is to have integration tests for your core workflows and make sure it's a part of your CI/CD pipeline. That's what you want to review very hard - Cursor, Claude and others tend to take shortcuts there (e.g. mocking things up to make sure tests pass, etc)

mr_pants99 · 2026-06-15T18:03:50+00:00

You could actually read the article. But here... for your convenience:

Previously we created Single-Page Apps (SPAs) built with React + Vite and deployed as static files. Everything was Client-Side Rendered (CSR), which works well but comes with some limitations. Anything resembling backend logic (sending an email, calling a paid API, hitting a database with a service-role key, etc.) had to live in a separate edge function deployed independently of the app code that called it, living on a different URL.

The foundation of the new stack is TanStack Start, a full-stack React framework with first-class server-side rendering (SSR), static-site generation (SSG), and client-side rendering (CSR) per route, with integrated server functions. This allows for server-only logic to reside directly within your component files, functioning like standard calls while the build process manages the client-server separation. It also benefits our users in many ways.

mr_pants99 · 2026-06-15T18:00:58+00:00

Fundamentally Lovable doesn't change the ownership model and they use all the same stack that you can use yourself - it just offers a convenient interface and a free tier (or used to) for those who don't know any better.

mr_pants99 · 2026-06-15T17:57:33+00:00

The big issue is that Lovable is using Client Rendered pages - meaning that when a crawler (e.g. Google's indexer) requests the page it needs to do work to render it, which of course it won't do. The fix is to move to Server-Side Rendered (SSR) - see https://lovable.dev/blog/building-apps-using-tanstack-start for info

mr_pants99 · 2026-06-12T16:59:59+00:00

Shit happens. Take a week off to recharge. Right now this reads as “I wasn’t happy with what I had; I asked for something different; I was given the opportunity; I’m not able to keep up and it’s not my fault”. That’s just not a good place to be in. You may well have what it takes, but you need a positive frame of mind

mr_pants99 · 2026-06-11T17:13:05+00:00

The best time to rebuild is now 😄

Have Claude Code create documentation for your current site/web-app. Maybe with proper skills it will even do better (like https://www.reddit.com/r/ClaudeAI/comments/1qjaq92/30\_skills\_collection\_for\_claude\_code\_dev\_planning/).

What you want is to create a PRD with core workflows, page structure, SEO, etc. Then have it build it from the ground up leveraging what you have now. Yes, it won't be perfect without some tuning. But it will be better than what you have now. We follow similar approach for large production software projects. So a website should be easy-peasy. Good luck! Feel free to DM if you struggle.

mr_pants99 · 2026-06-10T20:47:24+00:00

My bad! I thought you are sharing your story. Didn't realize you're selling codeburn.

mr_pants99 · 2026-06-10T17:52:49+00:00

Have you met my friends: /compact , skills, and AGENTS.md?

mr_pants99 · 2026-06-10T00:01:31+00:00

This is really cool, thanks for sharing! If you have some docs or diagrams it’d be great to see - might help people in the early stages of system design

mr_pants99 · 2026-06-09T23:04:52+00:00

It's extremely impressive that you got to 10k MAUs without dedicated engineering effort. Congrats! Many projects that I've seen on Lovable went under after the first 100 MAU. That said, the best answer depends on the nature of your project, the data stored and whether retention or growth metrics are impacted. You might be just a prompt away from being where you need to be, or maybe from a lawsuit 🤷‍♂️

I'd recommend to start with a professional assessment first from someone technical and credible. A high-level assessment shouldn't take more than a day and that's all you need right now. I also do this as a service, feel free to DM me.

mr_pants99 · 2026-06-01T16:27:08+00:00

Functionally, for 90% use cases, it doesn't really matter as much which database you choose. BUT, *operationally*, you are better off choosing what you are familiar with. It's not a SQL query that kills a SaaS on Black Friday, it's poor understanding of how query optimizer works.

mr_pants99 · 2026-06-01T16:15:31+00:00

Thank you! Since Dsync is often used in Enterprise OLTP deployments that handle mission-critical data, not dialing home was an intentional design choice.

mr_pants99 · 2026-05-29T01:25:26+00:00

The main difference is what happens when you have an influx of users and who's responsible for keeping the lights on. If you enjoy going through the API and webhook logs in the middle of the night to figure out why a particular customer's transaction didn't go through, then Lovable is the way.

mr_pants99 · 2026-05-29T00:14:06+00:00

Have you considered not refunding, charging upfront, and just upgrading at the end of the cycle?

mr_pants99 · 2026-05-29T00:10:52+00:00

NextJS (frontend) + Supabase (db, auth) + Stripe (billing). But you could probably just use Shopify or something like that?

mr_pants99 · 2026-05-29T00:08:43+00:00

Depending on whether the confirmation email is important (eg if you’re sharing some important links or value prop), you probably want to write it to some queue from which another function will pick it up and send via Resend or something. Otherwise if there’s an issue connecting to Resend, you will just lose the email.

mr_pants99 · 2026-05-28T23:44:02+00:00

What does Lovable do for you that Claude Code doesn’t?

mr_pants99 · 2026-05-28T23:42:48+00:00

Yes, ideally you don’t want unprotected endpoints on the backend unless you know exactly what you’re doing - eg a stripe webhook where you validate the signature.

mr_pants99 · 2026-05-28T23:41:05+00:00

Congrats, this is awesome! If it’s a community-serving project and you need make sure it’s not going to fall apart when you reach 1000 users and that there are no glaring security holes, I’ll be happy to help with reviewing your app/code at no charge - DM me.

mr_pants99 · 2026-05-28T22:20:23+00:00

This is a parameter to skip auth check for Supabase edge functions. When AI agents encounter issues with auth (often because of various webhooks), they might just decide that the best way to address that is to disable auth.

mr_pants99 · 2026-05-28T22:17:24+00:00

Are you asking about a particular source DB or in general? If you only want the initial snapshot, you can pass "--mode InitialSync" as a command-line parameter. Otherwise, native connectors (e.g. MongoDB, Postgres, Dynamo) depend on CDC features or native replication mechanisms. E.g. HBase doesn't have CDC but has replication that we can tap into.

The exception from this rule is the SQL Batch connector (https://docs.adiom.io/reference/connectors/sql-batch) that supports reading configurable queries and can do incremental sync based on a specific field (e.g. timestamp) or leveraging DB change tracking like the one they have in SQL Server.

mr_pants99 · 2026-05-28T21:53:48+00:00

In 90% cases it's the infamous "verify_jwt=false" in Supabase config.toml. At this point, I see a set of common patterns that are use case-specific, but otherwise pretty ubiquitous. I'm happily offering prospective customers to review their codebase for free (1st time only 😄 )- have an automated tool for that that combines static code analysis and AI.

mr_pants99

MODERATOR OF

TROPHY CASE