A reporter was being investigated for having access to classified information, and the toll records (what number called or was called, and for how long the call lasted) were subpoenaed.
The only reason Mike Gravel had a copy of the Pentagon Papers is because Ellsberg sought him out, so Gravel wasn't himself the "leak", and Gravel knew that the NYT and others already had a copy (they were publishing parts).
Right, but the documents were still classified at the time so he could have prosecuted for publicly disclosing them had he not taken advantage of his position to read them into the record. The point is that there is a Constitutionally guaranteed mechanism for Congressmen to disclose alarming classified information they have access to.
I'm not a grandmaster by any means, but these are things that I focus on:
1. Aggressively avoid techniques and abstractions that have produced bugs in the past. The "backwards conditional" is an example of this, in languages like C that will accept x = 0 as a conditional, it is safer to do 0 == x in an if statement in case you mistype. Mutability trips me up sometimes, so I try to never re-assign a variable. I keep links to the source code of key libraries in my bookmarks bar so I never have the guess how something actually works. Static analysis tools, and bug prediction tools [1] are two steps I haven't taken.
2. Seek out code written by experts and inspect it [2]. If I'm considering using a new language or library one of the first things I do is to search for large scale OSS projects. For a new language looking at some of the popular 3rd party libraries can be really illuminating. Especially if you're already familiar with the problem space.
3. two words: learn to fuckin' type.
4. Get familiar with what the history researchers call the Primary Sources. Not just the actual source code but the proposals, the specifications, and the research reports that are written by the people who conceived the tools that you are using.
For a high latency situation if you're text editing there is EMACS TRAMP mode, and probably others similar that buffer the file locally, which will also solve the responsiveness problem.
Exactly. In the modern world latency concerns so outstrip bandwidth issues that it's actually much saner to copy the whole file across the wire than it is to try to edit it locally. The curmudgeon in me finds that amazing sometimes.
Yup. For command line work I usually don't mind but for text editing I find any perceptible latency incredibly grating. SSHFS is another solution that doesn't need anything special installed on the remote end. It's a pity Plan9 didn't take off, I think it hides this kind of pointless drudgery.
I think the aversion is because the way that they line up visually is the opposite of the way that they are matched by the parser. I think everyone needs a dose of LISP to get over any problems they have with any frequency or arrangement of brackets/parens/braces. Anyway, having a function that compares two structs and returns 0 or 1 with a printf out to stderr is just gross in my opinion.
The behaviour I want is that when I've opened that app with the badge the badge should go away. All apps that don't follow that behaviour are relegated to a screen far to the right.
That will have to be addressed by the Chrome permissions dialog ... Agreed though, I think it would be wise to make the user type-in their CVC or something before transmitting the payment info.
What surprised me the most from Paul Graham's Yahoo article was he was "sitting in my cubicle". I don't see how you could make someone a millionaire, and then put them in a cubicle, and expect them to stick around.
As someone who has been in this situation more than once, a cubicle versus a desk versus an office is not the issue - the issue is, can you motivate people with work they are passionate about and an incentive/compensation plan they feel is fair. Once you have those pieces in place, the work environment usually doesn't matter as much (and to the extent it does, the newly motivated employees will take steps to fix it on their own).
