shannongreen

  alias qub="source <(curl -sSL https://raw.githubusercontent.com/jamonholmgren/qub/main/src/cli.sh)"

oh wait, you're that guy

There is evidence to suggest that living with even mild hearing impairment can accelerate cognitive decline (though I don't know if there is yet evidence that this can be prevented by using hearing aids).

No, it couldn't. And even if it could've, that would be impossible.

Believe it or not, places outside the US did do a 'real lockdown' for a lot longer than a month, and it didn't 'solve' covid.

Sometimes the best thing you can do is stop someone from writing code.

I hate this idiom every time I come across it. I like to look at the header file to see the interface and important documentation, and this just obscures it. Depending on your compiler it can make debugging a huge pain as well.

The code presented is trash and doesn't follow best practices - using the type system, descriptive variable names, etc. Void pointers for everything, are you serious? Of course it's hard to understand. Revealing that it's the generated code doesn't make me any more comfortable with it.

Yes, I get that you shouldn't care what the generated code looks like if you trust your input, but I don't find the predicate any easier to understand. How do I know that's correct? What if I need to debug this generated output?

You cannot possibly be saying this with a straight face :)

As a professional embedded developer who uses bitfields to access registers every day, this doesn't really make a practical difference. On any bare-metal or embedded project you will rely on the behaviour of your compiler, and portability is largely irrelevant if you're accessing memory-mapped registers. Probably, the manufacturer has already provided register maps using bitfields anyway.

  Whenever you're called on to make up your mind,
  and you're hampered by not having any,
  the best way to solve the dilemma, you'll find,
  is simply by spinning a penny.
  No - not so that chance shall decide the affair
  while you're passively standing there moping;
  but the moment the penny is up in the air,
  you suddenly know what you're hoping. 
  -- Piet Hein, "A Psychological Tip"

The printed keys don't mean much - to learn to touch type correctly you shouldn't be looking at the keys anyway. I used a few typing games to start and then switched cold turkey for a few activities that didn't require speed (like responding to emails). It was, indeed, very frustrating.

That said, I don't recommend switching for most people, because you will get much worse at QWERTY and when you occasionally need to type it (like on a colleague's keyboard) you will appear incompetent; you will ruin your muscle memory for keyboard shortcuts; and, because standard Dvorak is not great for programming IMO due to the position of the [{ and }] keys. But now I'm in too deep, and I know from experience how hard it is to switch so I don't want to switch back!

Your browser's language is set to English. Do you serve UK, US, Australian or Canadian English?

hopefully mAh

I don't think this is correct. All hearing aids do work this way, and I also don't know of any way that (electromagnetic?) induction could be used to deliver sound.

In a person with hearing loss, not all frequencies are affected equally. Hearing aids can compensate by

1. Amplifying the affected frequencies (this is by far the most common approach) or

2. Compressing and pitch shifting the sound to a range that the user has better hearing.

I strongly agree. I'm always surprised how much resistance to this idea I encounter, though.

I still agree that we shouldn't call it air-gapped, though.