I think this person needs to lose an election.
I think this person needs to lose an election.
What about setting up roadblocks for a city of 200,000 people based on one localized shooting incident? It's not like San Bernardino is some tiny village, after all.
It'd be like closing down five blocks surrounding a liquor store hold-up. Either the government is grasping at straws, or their purpose for this survellance is pretty much unrelated to the incident.
What does Neil deGrasse Tyson have to say about racial diversity in astrophysics? That's right, nothing, so who fucking cares??
False. Neil deGrasse Tyson has an amazing story which is exactly about diversity in astrophysics. You can watch it for yourself here.
Factchecking is for winners.
PS: this is pretty obvious while unit-testing but I'll make it clear to avoid any confusion... the real implementation of SSLHashSHA1.update() and SSLHashSHA1.final() would not be called in this unit test, as that'd be outside of the scope of it.
At least Apple's bug could've been caught with basic unit-testing. This is the snippet of code from Apple's bug:
SSLVerifySignedServerKeyExchange(SSLContext *ctx, bool isRsa, SSLBuffer signedParams,
uint8_t *signature, UInt16 signatureLen)
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
Just implement a unit test with the following logic:
1. When SSLHashSHA1.update() is called, DO NOT return an error.
2. Expect 2 calls to SSLHashSHA1.update() and check the input parameter on each call.
3. Expect 1 call to SSLHashSHA1.final() and check the input parameters are what you'd expect.
That simple unit test would've caught this issue without any need of duplicating code.
See, that whole union thing bugs me.
If you're Senior only because you've been there long enough, but you don't have the chops to show for it, just get the fuck out of the way.
You people will get your nose bent out of shape at any goddamn thing, won't you?
Gender shouldn't matter when it comes to writing code, period. Turns out, it does in some ways that are not good for the industry as a whole. We're missing about half the insight that the inconvenient gender (aka "women") could bring to the table if the tech industry wasn't a sweaty jock party.
So, Google is trying to do something about it. Might be the *wrong* thing (I don't think so, but I'm not omnipotent) but at least THEY ARE TRYING TO DO *SOMETHING*, which is a lot more than I see any of you other meatsacks doing. You can either start being part of the solution, or just go to Hell.
If it gets more women coding, then more power to them.
If it gets more women in tech, more power to them.
If it will shut up your goddamn special snowflake whining, full power to them.
Emotion is a fact.
I take from this short statement the same sentiment that Bruce Schneier was speaking about, when he stopped whining about how everything "security theater" was completely irrelevant, and started exploring the real and tangible impact and importance of the feeling of safety IN ADDITION TO actual safety controls. You cannot just dismiss grandma's warm and fuzzy acceptance of strict authoritarian searches, you have to actually include it in the calculus, the whole of which can inform the security methodology.
Security is both a feeling and a reality. The propensity for security theater comes from the interplay between the public and its leaders. When people are scared, they need something done that will make them feel safe, even if it doesn't truly make them safer. Politicians naturally want to do something in response to crisis, even if that something doesn't make any sense.
Religion is the same: you can't just dismiss religion, it's a palpable phenomenon for a large number of stakeholders. Often, you can coexist with their philosophy while still doing real science. Galileo wasn't locked up in house arrest for his science, he was locked up for being an ass to the church. The church actually had little problem with the already-common views on the shape of the solar system, and would have "come around" on the matter much faster without his goading.
So, we all know how well this worked out for Dmitry Sklyarov last time. Learning how DRM is a self-defeating technology is kinda like the cycles in the fashion industry: everything old is new again. The stakes just get higher and higher with all the maximalist lobbying that goes on between each cycle.
Funny that for all the bitching about the "chiclet" style keyboard back then, now I see way too many laptops (and even Macs) that are using what looks like the same style. I hated it then, and I hate it now.
I definitely should have said this in my other post. I laugh and laugh at the Mac's chiclet crap. They're horrible to use for touch typing, just one step above a membrane keyboard. Yet everyone "loves" them because Steve Jobs told them to.
I swapped my chiclet infrared keyboard for the heavy-ass IBM keyboard right away. As soon as Macs went to chiclet, I bought two of the last heavy-ass Apple bluetooth keyboards; one for today and one as a spare, to use them through the years.
And it's nothing like the command line, which does no interpreting, refining or clarification at all; it just executes a limited set of commands exactly as entered, with no room for so much as a misplaced comma.
ZORK I (1979):
> unlock grating with key
Which key do you mean, the skeleton key or the rusty key?
The first sign of maturity is the discovery that the volume knob also turns to the left.