throwaway3neu94

Just following basic rules of thumb (minimizing current loop area, length matching, impedance matching through trace width, series termination, etc.) may yield a working device, but how do you learn from that?

At some point you're already applying all those rules of thumb, but how do you then actually measure what works and what doesn't so that you can improve beyond that?

It seems it is difficult to find resources teaching that, and also the equipment needed becomes very specialized and expensive fast.

I have read that even though there are no hard rules, after getting an employment based Greencard, one should stay at the company for another 6 months to avoid problems during naturalization. Is this true?

On two occasions, once after skiing for a week and once after playing flight sims an entire Saturday, I had an intense (and very nice) feeling of gliding down a (glide)slope as I fell asleep.

The website actually started as a sort of joke by someone in the kernel community. Then it stuck around.

For example, I found it useful professionally. We're releasing a new hardware model. We're doing some in-depth performance tuning/evaluation. To understand our performance characteristics, I needed us to break down the performance change into improvement due to new hardware and reduction due to new mitigations.

Linking this page in the Jira issue was the fastest way to get the point across what we needed to look into.

It is not, at all, something I would ever recommend to lay people, or use in the actual shipping product.

Depends on the criteria. Do automated reviews count?

I set up build+test via GH actions and have GitHub run them on PR's. And make all changes through PR's.

This not only prevents "forgot to run tests" type accidents during regular development, it also helps me when I come back to a hobby project months later, and it lets me confidently do small changes (think version bumps) directly through GitHub's editor, which saves a bunch of time.

And when, against the odds, I actually do get a contribution, the infra is already there and it really cuts down my turnaround time to get it merged, bump the version and deploy the release.

Of course if a single direct push yields you the badge then I guess pretty much every solo dev gets it sooner or later. But that indirectly turns it back into a good badge, right? "Independent enough to have a life outside a standardized corporate process"?

Fortunately that's not something you can buy.

These contacts are occasionally scheduled with organizations (schools etc.), but unscheduled for the general public.

Exchanges tend to also be one short question (how does earth look from above right now?) and one short answer (earth looks beautiful), and then it's on to the next person. Not just due to congestion, but also because the ISS is only visible for a few minutes.

No, you can use do{}while(0) usually. You only need statement expressions if you want it to evaluate to a value as well.