majelix
Here's the full quote: "Bill Gates spent thousands of hours learning how to program computers—but he only had that opportunity because he had the good fortune of having parents who supported his education."
I think you're in violent agreement that 10,000 hours isn't sufficient.
That's a major point of the article, given it's discussion of the spillover effect: "The bottom line: Practice self-control in one area of your life, and you can apply it in other parts, too."
I dunno, seems like way more work to come up with, maintain, and actually use the generator. Seems easier to just click a bunch in my vault to generate and copy, although I guess you're protected from vault-theft?
Given your example, I had already figured out all the way up to ies/otto are probably foreign numbers (more specifically, otto looks like 8 and 16 looks like double of 8) before even seeing that you just gave the answer away.
For 1, it's mostly about knowing yourself. What projects interest you, and where can you contribute?
For 9, it's convincing the owners that your contribution is a net positive. Start with 2: Check out how to contribute, and proactively reach out so your pull request doesn't come out of the blue.
Oh, and be willing to put your ego aside -- it can be tough to defend your work, particularly if you're a new (and thus haven't built up trust) contributor. It gets easier, both as the project learns to trust you and as you learn the work within their practices.
That's a feature, not a bug.
Limit your first reading to basic understanding of the plot and setting; ignore exploration of "deeper" themes until subsequent re-reads.
But if you're salaried, it's an arms race. Employees willing to work extra hours get more done (or at worst, only appear to get more done), and thus will get the rewards and promotions.
How would you characterize the COO then?
For starters, Microsoft does not have a monopoly on game consoles.
It's worth noting that in such an environment, he likely controls the client machines themselves (ie, only corporate machines on the corporate network), so it's straightforward to just push out a trusted Certificate Authority and intercept anyways.
This is that fuzzy line between behavior driven development and test driven development. Sure, you may not be able to write cukes to test how that your social mortgage site is going to work, but you probably should be writing tests to ensure that your internal compound interest code is correct.
Agile has the concept of Spikes (http://www.scaledagileframework.com/spikes/) for researching new problems. The key point that code is thrown away after completion -- this gives you the freedom to ignore normal methodologies and not have to worry about technical debt.
Presumably, you then go back with this new knowledge and only now concern yourself with writing supportable code.
This is true for the United States Postal Service as well. I've always thought it'd be interesting to look at what historically brought about the strong privacy expectations to postal mail when it's technically so easy to intercept.
This sounds more like ability rather than choice. It seems odd to demonize the U.S. because practically all Internet data flows through their territories.
> So just stop, stop making excuses for the US or the NSA
I'm not making excuses, and of course it's a Bad Thing. But don't pretend that avoiding one actor is really a solution, any more than rebooting your computer is going to solve deeper issues.
Why do you think this is? Do you really believe these efforts are not being taken by every major world covert agency?
If your vendor doesn't do a decent job verifying who you are (and this may or may not mean EV), then browsers won't treat the certificate any differently when it's entirely replaced by someone else either.
The flaw basically being that people aren't trustworthy, yes?
Do you have any alternatives? There's ssh's model, where you just hope it's the right certificate the first time; or maybe mob-source it like WoT?
Except that SSL isn't just about transport-layer security, it's also about identity. The entire model of SSL breaks down if anyone can buy a certificate for anything.
Of course it adds something: It makes it more difficult for someone else to go buy a SSL certificate in your name. Security isn't just about driving sales, it's also about protecting yourself and your customers.
Others may use in-house solutions. Here's Bank of America's two factor solution: https://www.bankofamerica.com/privacy/faq/safepass-faq.go
We're almost to a point where the question isn't whether or not they support it, it's finding out that they have a program, clicking through tiny text links at the bottom of pages, and figuring out how yet-another-implementation works.
Absolutely not. But you don't have to shout every secret you have access to (relevant or not) from the loudest possible podium either.
The key point here is that they call the police, not blindly dump thousands of private documents onto the internet.
Looks like computer technicians get paid plenty well. According to at least one random google search, entry level SysAdmins make nearly $20k more than entry level auto mechanics.
Anecdotally, I don't know a single person in the IT field who isn't flooded with recruiter-spam. Meanwhile, the economy and unemployment rate remain huge political and news topics.
Sources: - http://www1.salary.com/Automotive-Mechanic-I-salary.html - http://swz.salary.com/SalaryWizard/Systems-Administrator-I-S...