HackerTrans
TopNewTrendsCommentsPastAskShowJobs

ronvoluted

no profile record

Submissions

This Pokémon Does Not Exist: Using AI models to create fake cards that look real

huggingface.co
18 points·by ronvoluted·4 года назад·8 comments

comments

ronvoluted
·4 года назад·discuss
Max Woolf, the person who fine-tuned the image model (not me!) posted a bunch of just the Pokémon here: https://twitter.com/minimaxir/status/1470913487085785089

The thread melissalobos posted above has a lot of replies with people sharing their cards too.
ronvoluted
·4 года назад·discuss
Agreed, lots of chaos though also lots of fun. Some of these even have 30HP and then an attack that does 30 damage to itself.
ronvoluted
·4 года назад·discuss
Thanks for that! It was down for a bit and is back up now.
ronvoluted
·5 лет назад·discuss
That's awesome and yeah Steph sounded great from your podcast chat! Thanks Lee :)
ronvoluted
·5 лет назад·discuss
Hey Lee, just listened to your chat with swyx the other day. It was great hearing how Vercel positions itself and your thoughts on devrel!

I know Vercel has a great developer relations team already— what would the appetite be for more Svelte DevRels in future? I've been working as a developer advocate and love Svelte enough to have even given talks on it. Would be an opportunity I could see myself in for years :)
ronvoluted
·5 лет назад·discuss
I won't repeat what others have said about advances in natural language processing since 2017, but it's true that it's a solved problem if your problem isn't "perfect search" but a more realistic "excellent search".

> Use existing technologies first: As in most engineering problems, don’t reinvent the wheel yourself. When possible, use existing services or open source tools. If an existing SaaS (such as Algolia or managed Elasticsearch) fits your constraints and you can afford to pay for it, use it.

I work at an AI search company (Relevance AI) and even we see that InstantSearch.js is all some people need in terms of UI. We created a version of it that uses our NLP-backend but is still the same Algolia components on the frontend: https://www.npmjs.com/package/@relevanceai/instant-relevance

The reason was because those components work. Think these days you'd need to ask a lot of questions before completely rolling your own UI or NLP handling.