gknoy

> We "log in" by running a Python script that pops a root shell.

I'm surprised that when you do this, you can't then set the root password. (Also, holy cow. What a durable machine.)

I find that fascinating, because interacting with the tests in our codebase (both Python and JS) answers a _lot_ about "how is this meant to work", or "why do we have this". I won't say I do test-driven development, at least not very rigorously, but any time I am trying to make a small change in a thing I'm not 100% familiar with, it's been helpful to have tests that cover those edge cases. :)

> My dotfiles are private for now cause I need to clean some commits

I had to do similar. I ended up deleting the git history and just recreating it before pushing. The best thing was to add a dependency on `~/.secrets` or other similar un-tracked file, which is basically just a source-able script that defines things like API keys, private URLs, etc.

You weren't kidding. I was amused by the humor in the first few minutes, but then I got to its showcase of what you can do, and am just even more blown away. They weren't kidding about doing _just about everything_ pretty well.

> every time it's like I'm reading it for the first time. I can only remember thew "mood" so to speak,

I am like this with a lot of books. I'll remember a very high level overview ("The Historian is about a modern day hunt for Dracula, and it's really cool, and I liked how the story was told, but I can't remember why or any of what happened."), but can't remember much about plot details.

It makes re-reading things fun, but also is frustrating because I can't explain why something was good, and I also remember just enough that plot twists don't surprise me the second time. It also means that I completely forget about the "bad" parts of the book, or the parts that didn't resonate with me.

I appreciate you laying it out like that. I've seen these NVME NAS things mentioned and had been thinking that the reliability of SSDs was so much worse than HDDs.

Wow. This is amazing. I really like the way you use color and do footnote-like explanations.

Thank you for painting it that way. As someone who has normally done back end stuff in Django, having the ORM magic is so deeply ingrained for me. I was about to ask what one should use for an ORM, but looking at the Hono examples is pretty helpful. It looks Prisma is one good example of what I was looking for :D

I really like that your page talks about _why_ a Hilbert curve is good. I don't remember ever learning about those before, and now hopefully if I'm ever trying to visualize 1D data, I might remember that :)

This seems like it would be solved completely by printing the error message ("option b unknown"), and then also printing the "--help" stuff. You can see the error inthe first line(s), so `head` will make that easy to see, but anyone trying to print the help text will get it.

This is somewhat off-topic, but I am blown away by your use of uncommon characters like "①". They stand out so much that they (for me at least) make referencing parts of the code snippet so much easier to follow.

I see these _nearly never_, so rarely that I forgot they were available to use. I didn't realize HN supports them, or that I could probably use them in review comments on Github. Thank you for the inspiration! (now to figure out how to actually type them...)

I believe they mean a cover as in a case that has a folding cover, not as in the external layer of the phone itself. So you effectively turn that otterbox-ish thing into a faraday cage that will enclose your phone.

I am not sure how I follow how that isn't completely negated as soon as you go to actually use the phone, though.

> show their QR code to vendors who scan it to charge their account.

That sounds _brilliant_ -- being able to show a physical QR code card rather than dig out the phone sounds like it would help a lot with preventing damage/loss of phones.