Brainstorming traffic; product diary & public build.

Yesterday I took a break and today I'll think about how to generate some traffic and collect feedback.

I took a look at PostHog. Not much traffic, maybe 20 users clicked through at best. Almost all of them seem to leave as soon as they're prompted with the login screen. Should I set up a demo that doesn't require logging in? I don't think that's feasible with the "one vm per user" setup i have going on right now. Maybe I can try and figure out how to run dotnet in the browser? I know it's possible, but it will probably take a ton of time to get going. Maybe just have the content available without the code editor, and display the login button instead?

Anyways, let's focus on generating more traffic. I shoud start by posting on reddit.

I searched for "boot.dev for dotnet" and found a few posts. I also noticed boot.dev has a lot of articles posted on their website. Maybe I should repost my popular medium articles on codeinteractive.dev?

I think I should be building this in public. I have an idea of posting these daily updates on my personal page, and weekly summaries on linkedin. Maybe that can generate some traffic? People like seeing others fail (lmao), so maybe that's an idea? Watch me struggle as I try to build a product?

I submitted 2 comments and one post, but most subreddits I checked out have a rule against advertising.

Today's efforts weren't that fruitful. I spent most of the time brainstorming and aimlessly looking around. But I think making this diary public and having the content available without logging in are good ideas. I'll iterate on that more tomorrow.