Back after it

One of the things that's been gnawing at me a bit recently is this project. While I'm ambitious an optimistic about Tempstore, I've also thought about how close to finish this project is.

I initially stopped working on Rely because I got scared of some of the technical challenges of building a highly available system on my own. There were a few things in both scheduling and multi-node parts of the app that made me think: "it might be too hard".

Devs vs Normies

The other thing is that Rely is focused more on developers and technical audience and so I guess I'm worried about my reputation if I get it wrong or build something that's not up to my own high standards.

Rely is also a bit more boring when compared to the flurry of AI hype that could propel Tempstore. Tempstore's audience is more regular people, and so I thought that the TAM might be higher, and therefore easier to get to scale.

Having time to mull over this has lead me to realise that there is in-fact ways to build in AI into Rely too. Something that wouldn't be too gimmicky but actually useful.

A New Hope

Spawning from a recent podcast talk, I'm not realising that if rely is so close to being functional, I could get it to a point that it's operating and then start to market. Even if it provides basic functionality, it could be enough to get some users while I build tempstore.

So I've allowed myself 1 week, maybe 2 max to bring the final parts together on Rely and get it out to the world.

Frankenstein

My marketing plan is now to get it operational, create a "Free Uptime Badge" type feature and then point paid ads at the thing and see if it jolts to life.

Let's see, I'll update folks on here with the progress.