How Pavlov’ed do I have to be, that I immediately think “Naggle” when I see a blog post about request latency, even though I never had to debug such an issue
This is an educational and well crafted puzzle that just takes a few minutes to complete. I learned something.
I think there are many conclusions that can be drawn from the solution to the puzzle, but I don’t think Lobsters has a way to discuss it without spoiling it.
the past couple months of posts here and on HN have prepared me for this - 50ms has become quite a popular inexplicable latency.
How Pavlov’ed do I have to be, that I immediately think “Naggle” when I see a blog post about request latency, even though I never had to debug such an issue
Nice game to demonstrate a common weird issue. Is there a framework or it’s built from scratch?
It uses Twine. The source is here https://github.com/jvns/twine-stories and I wrote a blog post about the project here https://jvns.ca/blog/2021/04/16/notes-on-debugging-puzzles/
…this is giving me a lot of teaching ideas.
This is an educational and well crafted puzzle that just takes a few minutes to complete. I learned something.
I think there are many conclusions that can be drawn from the solution to the puzzle, but I don’t think Lobsters has a way to discuss it without spoiling it.
Rot13-ing spoilers is the classic technique.
Va cenpgvpr, guvf cnegvphyne ceboyrz pbhyq unir orra nibvqrq ol whfg abg hfvat WninFpevcg.
Thanks, this was fun.
That moment it clicked: https://i.imgur.com/Pc0p9OJ.png
that was great - I would love to do more of these!
very cool pedagogical technique
Amazing, thank you for sharing.