Yes, well LA's part of the US, isn't it? Why should some people's votes count more than others because they are spread over a larger geographical area? The reason for the E.C. is the Compromise of 1787 (look it up) which was needed to get the constitution ratified, not due to any far-seeing genius move to safeguard federalism.
Yes, the institutions have to be more important than any candidate or political principal in order for the system to have legitimacy. But it has nothing to do with democracy, republicanism, federalism, or any other legitimate political aim. It's just the rules that we had to agreed to in order to have a country in the first place.
I am a liberal who is dumbfounded and heartbroken by the election, but I would NEVER criticize any smart people for working for the new administration. Trump will be by far the least prepared and qualified President in the history of the country and I want him to have the best advisers possible. The extent to which he is capable of listening to them will determine how much or little damage to our civilization will suffer in the next few years. I've no illusions that the political causes I support will be devastated, but at this point its about survival.
I see an AI treating the kill switch something like RoboCain treated the remote here:
I'm tooting my own horn, but you might find my article on long-term password hashing strategies helpful:
1) Use a one-way collision-resistant algorithm developed by professional cryptographers, and the implementation of which has been adequately studied and understood;
2) Do not use an algorithm with known vulnerabilities (this obvious step is sometimes not followed);
3) Use randomly-generated data—salt as additional input to the algorithm to minimize vulnerability to rainbow/lookup table attacks. The salt should be generated from a Cryptographically Secure Pseudo-Random Number Generator;
4) Use a long salt, preferably as long as the output of the hash function;
5) Use an adaptive hashing algorithm—that is to say, an algorithm with a configurable number of encryption iterations to slow attackers (a.k.a. key stretching). The number of iterations can be tuned as the speed of available hardware increases to keep the resulting hash secure. Such choices include PBKDF2, bcrypt and now scrypt.
6) At at some point you will need to change your hashing function, in fact, probably many times. So store the algorithm along with the hash e.g. ALG:HASH:SALT
7) secure legacy hashes by wrapping the obsolete hash with a new one e.g. encrypt the md5 hash of the guy who hasn't logged in for years in your new hashing algorithm and store it with a token like md5|pbkdf2:hash:salt
This doesn't have to be complicated. All Google has to do is release their hiring statistics to a trusted third party, who interviewed during the last few years and who was hired for each position. Then the third party can investigate and find out the ages of everyone (which won't be hard). Then break it down by age group and see if there is a difference between how well applicants succeed based on age. This won't happen because I'm pretty sure Google knows how it will look
That's probably due to the vast number of Java devs who have been doing it for many many years. Try Node.js, Rails, or Django; these are newer platforms where you won't have to compete with the same number-of-years-with-my-platform issue
I don't know where you are located, but have you considered applying to Dev BootCamp/App Academy/Hack Reactor or another such organization? From what I read they get their grads good jobs.
Two things every programmer should know (yes, this applies to you):
1) You are not smart enough to write your own crypto, so don't
2) You are not smart enough to write your own memory allocation, so don't
Yet magic and hierarchy arise from the same source, and this source has a null pointer.