"consumption-to-creation ratio" are words i've never put to that positive feeling of choosing to code over watching another TV show or the negative feeling of the alternative choice.
recently i feel like vibe coding is a cheat code in this respect - i can code while watching TV... and a few times the output of the vibe coding exercise was interesting enough to switch to full attention coding.
when i track nutrition i always get stuck on things like "are the values for a chicken thigh with the bone in or out? do i weigh the meat pre-cooked or after i cook it? do i weigh the bones after i'm done eating and subtract that from the initial weight?" im probably overthinking it.
love the look and i'll keep playing with it but right off the bat i ran into a couple issues:
when i start typing on the search box on the home page it eats the first character (so as i type chicken, what shows up in the next screen's search field is just 'hicken'). and when i search for chicken thigh i don't get any results - seems to just stop filtering? when i press enter in the search field when "chicken thigh" is entered i get a "something went wrong" error.
Thank you for your kind words and feedback. The search should be better now, and is much better in-app with additional local caching.
I can assure you that you are not overthinking it in terms of figuring that information out. The search experience tries to make it as clear and helpful as possible. If you encounter any situations where it could be more clear, I would love to see them. My contact info is in my bio, or there is a feedback prompt on the site/in-app. Thanks again for checking the project out and your feedback.
latest in my vibe coding adventures is an infinite word search game. click and drag when you find a word.
the grid of letters is pseudo-randomly generated by coordinate (so it is deterministic) and the game seeds actual words in every 10x10 sub-grid. these are also pseudo-random.
this was an idea for a game i had back in 2023 but never executed on.
tonight while binging dune prophecy i vibe coded it and after a few episodes i had something worth sharing.
all these experiments are just me chatting with o3-mini-high, pasting into an editor, and testing in a browser.
the longer i iterate the further off the rails it goes and i find myself reiterating previous requirements. i imagine with some customized prompting you could better keep it consistent with established requirements.
reply