u/DeadGossip

So serious question, I've been contemplating a lot. I've been calling what I'm doing vibe coding because I don't have technical schooling, but when I looked it up it seems it means just not really trying to understand the code. Blindly trusting what its doing. That's not really what I've been doing.

I make sure I can understand it even if I can't read every line of code. I test the shit out of it. I make it give me weekly analysis on the code looking for duplicates, dead code, hard coded values that should be config, etc.

Is it still vibe coding? Are other people who vibe code not really testing or telling it how to make the pieces work together?

Everyday the list gets longer of what a perfect platform would be. I have mostly used Ancestry and family search so my experience is limited. They just feel old and overwhelming to navigate.

Also like is being connected to all trees a blessing or a curse. For every gem I find, I also spend a ton of time clearing through duplicates. I also just made the mistake of accepting too much garbage early on 😭

Please tell me im not alone!

30 days in and I just opened my waitlist.

I’ve got about 4 weeks before I let test users loose, so I figured it’s time to stop building in silence and actually talk about what I’m doing.

Everyone talks about building the product. Nobody really talks about everything after you have something working:

Terms of service
Privacy policy
Cookie stuff
LLC, DBA, trademark
Business bank account

That part nearly took me out this week.

At the same time, I started focusing way more on getting plugged into communities instead of just building alone. I’ve been writing on Substack for a year mostly into the void, but recently started actually engaging with people in genealogy. Applied to Daughters of the American Revolution, joined Reddit (which I somehow missed until now), and started talking to other builders.

That’s where the real value came from.
A lot of my best features came directly from problems people were venting about.

Now it’s just: build, listen, repeat until June.

Day 30
Hours in: 68
API costs: $26.63

If you’ve launched something recently, what hit you harder: building the product or everything around it?

If you’re into genealogy and want to test it early, I’ve got a waitlist open. Happy to share the link if there’s interest.

I am looking for copies of my great grandmother's marriage record. She married in Chanute, Neosha, Kansas in 1917. So far all I can find are newspaper articles about it, but I am having a very difficult time finding anything recorded, marriages, births etc. Anyone have tips or tricks or know of some good free resources. I checked the usual suspects FamilySearch & Ancestry. Appreciate any assistance!