Hey, thanks for the reply! I have actually been fighting the low contrast and what i feel is the biggest problem on both light and dark themes is the small text.
I will release an update soon addressing both the low contrast and the small text, both to improve legibility.
I'm sorry the gray text hurts your eyes, I admittedly haven't recieved much feedback at all, so any observation is appreciated
I started 5 years ago via a programming bootcamp here in Portugal. After finishing it, I dreamed of being able to make my own software, and solve all my programming and life problems in one fell swoop. Then the AI boom happened, I got laid off after 2 years of working at a software and consulting co., and swallowed my dream of making enough money to buy a house (lol).
Currently working in a place where I actually need to talk to people and do real life stuff: a store clerk. Not glamorous, but it allows me, in my own time, to tinker with the things i know, learn new things, and more recently, vibe-code stuff and release at a pace I've never worked before.
What i meant by the "public vs dev mode" is: i gated a feature or two behind only being present if im running my app locally (via npm run dev or what have you), because i was insatisfied with how that feature is currently implemented. I intend to refine it at a later point.
I did that because, even in the age of thinking "in terms of features rather than implementation", i am trying to be selective, and find a headspace where, if i feel that a certain aspect of a project (be it fully/partially vibe coded or not) is not ready to be presented in the live app, then it does not need to / should not be in prod. Could be that i was aiming too high and the feature was lacking, coule be my prompts that were misguided, or could be feature creep making me nervous.
I both welcome and fear the age where tokens get vastly expensive. I also hope for the time where we can run proper local models that don't require me to live in a data center.
Sorry for the long comment. It's my own writing at least.
"if i had more time, i'd have written a shorter letter"
> With an AI assist, there was no reason to stop adding improvements as I thought of them, so I didn't.
That is the mantra of today, yes. In a similar vein, I made my initially personal C course into something I could make public-facing, with some refinements, I also kept adding features but them my "sanity"(?) kicked in and i squashed a couple to be only in dev mode. Perhaps they will return to the public version after a round of refinement.
This is the epitome of "my idea didn't get stolen, it just got tired of waiting"!
Just kidding (although I did have a similar idea for an app a couple months ago but didn't end up fully commiting to it.)
Anyway this is a pretty useful idea. What made you start off creating it?
I have returned and to my pleasure, all types appear to be implemented, and Pokemon are matching the type!
Not only that, but I seem to have found a Shiny Sligoo on my third spin or so! My dopamine has never been so high.
Good job OP. Thanks for not giving up.
Hi HN! I would like to share a blog post i've wrote about Open Source contributions.
We know all about the README edits debacle. But I felt I needed to express myself regarding how to actually approach contributing.
Full disclosure in case it wasn't obvious: the blog post has edits made by a ChatGPT extension called Blog Writer.
But I will defend that the initial 60% was comprised of my disorganized ramblings, because those contained my raw thoughts.
I'd love some critique, any constructive criticism is immensely appreciated. Have a wonderful day.
an interesting approach. some work to be done but i will keep tabs!
i will point out that 6 of the 18 types appear to be missing on the wheel, and the type that your arrow lands on does not seem to produce a pokemon of that type: my first spin landed fire, and a croconaw (water type) appeared (I think its rotated 100-120 degrees counter clockwise?)
but not to discourage you. will be on the lookout for the next update. gj op