throwphoton

Argh is this real or not? Would energy radiated away as a result of inductance be analogous to energy radiated away by gravitational waves in the "water pressure analogy"?

You would also need to avoid any and every other way of revealing your location.

Interesting. Not casting a void pointer return value seems like a bit of a shibboleth for the "C is not a subset of C++" community.

> So those 1 in 6 know exactly how it will impact them because it already has.

It could impact them differently if they contract it again.

> too much faith in dependency oriented programming

Which is why it's a distraction to even consider this particular person's track record.

Even if this same person pulled one critical package a month for the next year, the fundamental problem is still that the ecosystem in general relies on parties with no obligations to manage critical dependencies.

> I'll be in the pub by the end of the year.

Does this mean that you think the risk of serious morbidity or mortality is overestimated, or because you think at some point the reduction in social interaction is worse than the pandemic itself?

Wow...

> Google Buzz publicly disclosed (on the user's Google profile) a list of the names of Gmail contacts that the user has most frequently emailed or chatted with.

Google Buzz is something you definitely don't want to be similar to.

Any diagram like this should include an estimate of usage, and how much that usage will cost, for every "block of architecture" displayed. Absent that, it's impossible to tell whether it's a good idea or a bad idea.

Moreover the cloud providers should make it harder for an uncontrolled "block of architecture" to accidentally spend too much money. The focus seems to be on "always available", but depending on how fast it's spending your money, it might be better if it crashed.

Expanding further, perhaps each "block of architecture" should have a separate LLC dedicated to it to control billing liability. Incorporate your "lambda fanout" to keep it from bankrupting your "certificate manager" when it goes haywire, and let it go out of business separately.

What can you do with a void pointer without casting it, apart from comparing it to NULL?

You're missing the point by focusing on the job search information specifically.

Any information provided without a clear understanding that it would be made public should not now be made public by default, even if it is just a name and some badges.