HN user

ehaveman

22 karma
Posts7
Comments28
View on HN

this resonates.

"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.

interesting article but now im curious how this has evolved over the last 6 months with advancements like tool use and the new reasoning models.

couple more vibe coding experiments from this week: random maze pacman clone: https://emh.io/gpt/mazeman.html breakout with a slowly expanding voronoi wall: https://emh.io/gpt/voronoi.html

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.

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.

fun. good writeup. i tried setting up a custom gpt to run a game like anagramish.com - gave it the word list to choose from, instructions on the rules, etc - but no matter what i did in the prompt it would hallucinate start words or it would incorrectly accept invalid guesses (or mark correct guesses as invalid).

really enjoyed this demo of a tool that enables text documents to be gradually enriched with application features. think taking a recipe and making the quantities and durations interactive via some pattern matching and simple instrumentation.

can you provide some more detail? i tried reproducing and got very different results.

both chatgpt and the gpt playground return:

w2: creative w4: unordered

when fed the prompt:

r(man,young,age,old) r(man,rich, wealth, poor) now find w2 and w4 for r(_, creative,_, unordered)

this is very interesting to me because i am building a mind-mapping tool that is powered by GPT and im currently working on optimizing the prompts to get it to return quality relationships.

Pangram 3 years ago

How long before someone makes a pangram wordle-like game?

i was planning to use fly.io for my next project!

what are people using these days to deploy a node app (fastify/sqlite backend + vanillajs front end)? last time i deployed anything it was a rails app to an ec2 instance via capistrano - but that was eons ago.

Been a while since I did any real coding for fun and last month I had this idea for a new word game. Great excuse to learn and play with some new technology I don’t get to use at work like web components etc.

i was so hoping this was true i scripted it (paste this into your chrome console):

function keyDown(keyCode) { var e = document.createEvent("Events");

    e.initEvent("keydown", true, true);
    e.keyCode = keyCode;
    e.which = keyCode;
    
    document.body.dispatchEvent(e);   
}

controls = [ function() { keyDown(37); }, function() { keyDown(38); }, function() { keyDown(37); }, function() { keyDown(40); }, ];

i = 0; setInterval(function() { controls[i++ % controls.length](); }, 100);