505 karma · joined November 28, 2011
The avalanche effect (referred to in the last sentence) is important as a heuristic. Among other things, it makes it harder to go from an "approximate" preimage to an exact one. If we had f(x) = y, where y is similar to our target y', we shouldn't be able to find x' with f(x') = y' just by looking at the neighborhood of x. But this doesn't rule out more "clever" ways of tweaking x, and it doesn't obviously stop an attacker from deducing some property of x'. So for one-way functions, what we really want to assert is the nonexistence of an algorithm for finding (properties of) preimages, that is any better than just trying lots of new values of x.
There was a released-but-redacted CIA memo saying, "An Egyptian Islamic Jihad (EIJ) operative told an XXXXXXXX service at the same time..." From analysis of the size and shape of the blob, the missing text could only be "Egyptian".
In fact, a monospace font turns out to be harder for this; with a proportional font, as here, there is more variability in total word length due to the different letter widths, and so a greater ability to reduce the number of possible matches.
Perhaps in these oft-cited days of lego sets that are more like a few big pieces than lots of little pieces, people will start to think differently.
There is also the issue of how best to write the definition so that people can actually understand it. Webster's Second and Third New International Dictionaries included color plates (which seems reasonable!) but also gave HSB values in the Second and complex color comparisons in the Third (cerise is "a moderate red slightly darker than claret, slightly lighter than Harvard crimson, very slightly bluer and duller than average strawberry, and bluer and slightly lighter than Turkish red"). For the Learner's Dictionary, though, they used definitions like "green is the color of grass", less precise but probably still having some psychological truth - the color of grass is surely an anchor point for our concept of green.
Moreover, there is a hugely important signalling role in the selection: it is advertising, "here is our community, here's who we are, here are the problems we work on and the cool techniques we use". So the selection also takes into account things like: "people doing X should get to meet people doing Y", "we think more people should work on Z", and so on. Diversity among the speakers is part of this! Just as surely as you wouldn't want a program of people all from the same company - like it or not, the makeup of the speakers does send a message, and part of the responsibility of organizing an event is deciding what that message will be. It's also communicated by all sorts of other things, including the process for soliciting and choosing submissions, details of language and graphic design, etc. All of these things contribute to a general impression of what the community is like.
The claim of "coincidence" in this instance would be a lot more convincing if the procedures and language were there to back it up. I'm not even talking about affirmative action. I only mean that if you want to claim to be meritocratic, you have to do the work, not just cross your fingers.
Things look a bit different from the other side of the table, anyway; the original questioner's project is a tricky one but it doesn't sound like it's absolutely critical to the company. If he's not around then they can probably make do with somebody else (maybe a new hire), or just live with the old system. People come and go for all sorts of reasons, and it's the responsibility of management to cope with that. As long as he gives reasonable notice and cooperates with the process then there should be no grounds for hard feelings.
Well, yes, that's what conservative means. You're using stable distros, with older versions of Python, and it sounds from your original post like you're not interested in using newer versions right now. So... what's the problem exactly?