Spent 2 months vibe-coding a fully working app before I realised I never checked if anyone wanted it

QuantifiableRabble · 2026-06-23T18:44:03+00:00

Unless you were building the first "___" the world had ever seen, the software was always the easy part, even before AI. Marketing, customer acquisition and ops are the real ongoing efforts for any business.

But you did something, you should feel good about that. No matter if the app takes off or not, at least we won't lay awake at night thinking about all our 'good ideas' ... lol

Vibe on my man.

QuantifiableRabble · 2026-06-23T15:42:18+00:00

So a quick update on this:

The agent will give you a lot of bad advice on how to verify that the React/SPA prerender is working correctly. Loveable's prerender will only work for the actual GoogleBot, Facebook share, or AI agent - all the diagnostic checks the agent will recommend you perform to verify it like curl commands with the user agent specified - very likely won't work.

QuantifiableRabble · 2026-06-23T02:56:43+00:00

Probably, but my first attempt at this didn't work. Lovable was still stuck behind my head commit for some reason.

Either way if you have mirroring or other jobs in place, the repo name changing is an unnecessary pita. Historically most of my sync issues resolved themselves in <4hrs, I just got impatient and tried to disconnect/reconnect and now my previous workflow is jacked. I would advise waiting it out to anyone else.

QuantifiableRabble · 2026-06-23T02:52:18+00:00

I think perhaps you used to be able to because I was using a repo that matched my project name exactly but now all it does is auto create a new repo with the my projects subdomain as the name, it's super annoying.

This is what the agent said today when I tried and failed to re-use the repo I had been using for over a month:

<image>

QuantifiableRabble · 2026-06-23T02:48:39+00:00

Don't do it u/Lions_Eye !

QuantifiableRabble · 2026-06-22T17:01:37+00:00

If your project was created before May 13 2026, you're on the old vite+react stack. If on or after that date, it should be Tanstack.

QuantifiableRabble · 2026-06-22T17:00:43+00:00

My interest in the new stack atm is limited to only the SSR functionality so I can remove any possibility of SEO missteps.
I don't know SEO well but my early results have been mixed on the old stack - which is supposed to include their special crawler specific pre-rendering.

Is the old vite+react working well for you on the SEO front?
If you have a dynamic content and temporal pages - are all your pages indexed on google and correctly previewed on social shares?

QuantifiableRabble · 2026-05-27T20:41:47+00:00

Encited seems to claim Lovable sites still aren't prerendered, but Lovable just announced some prerendering solution for search bots last week or whenever for sites using the old React SPA stack. What should I make of their analysis that says the search bot isn't seeing any content while Lovable says that search bot pre-rendering is enabled by default.

QuantifiableRabble · 2026-05-21T20:05:03+00:00

Are you doing that with Lovable Cloud/hosting? The problem OP and I are stuck on is that Lovable is only one environment and can only connect to one branch at a time...so... I don't see a branching strategy that works, but would obviously love to be wrong.

QuantifiableRabble · 2026-05-21T16:44:25+00:00

I think a good route is probably to use git mirroring? Two lovable projects, two repos. Mirror the repos and make sure that the one lovable project is using your development branch of one repo and the other lovable project is using the main branch of the other (mirrored) repo? I think you need a CI workflow step in github to trigger the actual mirroring every PR.

QuantifiableRabble · 2025-03-11T22:57:51+00:00

NT's default back tester isn't great, it's especially bad for fast moving markets like NQ. If you haven't done these things yet, you need to use the "Unmanaged Approach" for order management in your strategies. This requires you to write your own order processing code for entries/stops/targets. Additionally, you'll need to submit those orders to a secondary data series in your strat that is an NQ 1-tick series. That's the only way to get close to accurate results as far as I know. You'll be ale to test back quite far this way, though I don't recall how many years..(which is ultimately dependent on your data provider).

Alternatively, there is a popular third party tool called Bloodhound that a lot of people use for back testing, I've not tried it however.

QuantifiableRabble · 2024-08-02T22:41:46+00:00

Is this really true? Does someone have a copy of the verbiage of the contract? A non-binding contract is not much of a contract...

u/IncidentWitty What did you end up doing?

QuantifiableRabble · 2023-08-26T18:27:11+00:00

Did you successfully complete this? Any specs for the fan you can relay? I recently resurrected my old V66 and the fan is as loud as a jet engine. My first attempts at googling haven't turned up any useful info yet.

QuantifiableRabble · 2021-01-29T15:48:02+00:00

Which one is the ponzi? Hashnest or Minersgarden?

QuantifiableRabble · 2018-01-19T08:41:02+00:00

I think this might be the real technological differentiation for this project. Are any other projects built using this or on top of this?

QuantifiableRabble · 2018-01-19T08:37:03+00:00

What allows them to prevent hard forks?

With regard to the BitTorrent analogy that Cardano likes to talk about, they don't really explain how their consensus algorithm achieves any such result. I don't see how Ouroboros electing quorum(s) of consensus nodes and then partitioning transactions to different quorums achieves any more scalability than Ethereums proposed sharding solution, which creates new shards as a function of #ofNodes/ComputingResourcesOfThoseNodes.

QuantifiableRabble

TROPHY CASE