Live data from Hacker News

Show HN: I built an AI dataset generator

github.com

21–30 of 36 posts

Re: Show HN: I built an AI dataset generator

#23

AI is really good at this sort of thing; I've been using an LLM with Faker for some time to load data for demos into SingleStore: https://github.com/jasonthorsness/loadit

Nice, I like the challenge video!

Ha thanks, appreciate that, I regret the video a little as I was going through a short "a more exciting blog with videos is what the people want" phase.

Re: Show HN: I built an AI dataset generator

#24
post #5

seen this pattern a before too. faker holds shape without flow. real tables come from actions : retry, decline, manual review, all that. you just set col types, you might miss why the row even happened. gen needs to simulate behavior, not format

This is well put. I once built a tool called [zefaker] (github.com/creditdatamw/zefaker) to test some data pipelines but never managed to get a good pattern or method for generating data that simulates actions or scenarios that didn't involve too much extra work.

Was hoping this AI dataset generator solves that issue, but i guess it is still early days. Looks good though and using Faker to generate the data locally sounds good as a cost-cutting measure, but also potentially opens room for human-in-the-loop adjustments of the generated data.

Re: Show HN: I built an AI dataset generator

#26
I wrote a Swift CLI app to generate dummy user profiles for an app we wrote (I needed many more than we’ll actually get, and I needed screenshots for the App Store that didn’t have real user data).

It was pretty “dumb,” and used thispersondoesnotexist.com for profile pics.

Re: Show HN: I built an AI dataset generator

#29

I used Anthropic's new Claude API integration with artifacts to make a probably-worse version that you can play with (after logging in of course). https://claude.ai/public/artifacts/eb7d8256-6d21-4c85-af9b-c... I used this GitHub repo as context and Claude Opus 4 to create this artifact

Haha, I find this kind of exercise telling for what's coming to the one-size-fits-all SaaS companies out there. I see a future where small teams can in-house the set of features they actually need, and a big drop in SaaS usage. Avoids the big vendor lock-in problems, unwanted features and bypasses all the accenture-style consulting fees.
Post reply on HN