HN user

Pinckney

1,344 karma
Posts2
Comments381
View on HN

That really sucks. They're supposed to just take a photo of the board and transcribe it later. I never touched a computer when I interviewed.

When was this? I think the chromebooks are fairly new in interviews, and it sounds like the interviewer didn't read the memo about how it works.

Maybe this is off topic, but am I the only one uncomfortable with the Post seeking names of interviewees?

The reports also omitted the names of more than 90 percent of the people who were interviewed for the project. While a few officials agreed to speak on the record to SIGAR, the agency said it promised anonymity to everyone else it interviewed to avoid controversy over politically sensitive matters.

...

The Post has asked a federal judge to force SIGAR to disclose the names of everyone else interviewed, arguing that the public has a right to know which officials criticized the war and asserted that the government had misled the American people. The Post also argued the officials were not whistleblowers or informants, because they were not interviewed as part of an investigation.

One of the key problems identified by this report is that military and government officials didn't want to hear bad news. People on the ground felt like they had to paint an overly rosy picture. The SIGAR report seems like an attempt to address that by enabling them to speak anonymously, but the Post doesn't seem concerned that publicizing identities may hamstring such internal government investigations in the future.

By default, Mercurial doesn't do any of these operations; you have to activate extensions.

graft is actually built-in, but that's beside the point. Coming from a rebase heavy workflow in git, things like updating a ref or abandoning a commit feel like fundamental operations, and when moving to Mercurial it wasn't obvious which of the built-ins or bundled extensions I needed to be reading about to do these things.

I did eventually find Evolve, as you suggest, but it's not one of the bundled extensions, and it's not something you'll find in the official tutorial, or "The Definitive Guide", or even in most of the SO answers explaining how to do git-like things.

By design, Mercurial makes it much harder to shoot yourself in the foot.

This is true, but git makes it so easy to recover from those mistakes.

That's what everyone says, but for me, coming from a rebase heavy git workflow, I've found Mercurial far more difficult to learn.

For example, with Mercurial, there's at least four different ways to do a rebase-ish thing: transplant, graft, rebase, and rebase (w/ evolve enabled). It's not obvious which a newbie should pick (rebase+evolve... I think?). Likewise, Mercurial has purge and strip which both delete commits in different ways. Git has multiple ways to do the same thing, but at least it's simple and consistent when you lift the hood.

Undoing any sort of rebase-ish operation in Mercurial also seems difficult and janky. It seems to take multiple steps, and involves unbundling some sort of patch file stored underneath your home directory. Whereas in git, you just update a pointer: `git reset --hard $BRANCH@{1}`. Git's reflog is such a fantastic safety net. Doing any sort of history rewriting in Mercurial feels very dangerous, in comparison.

You quote the militia act, but congress doesn't get to define the words of the constitution through ordinary legislation. If it worked that way then they could just as easily pass a law defining "arms" as only muskets, "speech" as only spoken words, and "unreasonable search" as only a search conducted without reasonable suspicion.

A report prepared by the Edison Electric Institute, “Out of Sight, Out of Mind, An Updated Study on the Undergrounding of Overhead Power Lines,” found that while most new commercial and residential developments across the United States tuck electrical facilities underground, burying existing above-ground electric distribution systems can cost up to $5 million a mile in urban areas.

They've linked to 2009 version of this report, although the numbers they use are from the 2012 version. If that confused anyone else, the 2012 version can be found here:

https://www.eei.org/issuesandpolicy/electricreliability/unde...

My understanding, from a quick 5 minute skim, is that it may be. It's being sent back to the district court for reconsideration.

Basically what seems to have happened is this:

1. Robles sued Dominoes alleging their website violated the ADA.

2. The district court dismissed the suit, saying the DOJ needs to provide guidance on the standards that websites must meet, if the court is to hold them to the ADA. They don't examine the question of the phone.

3. The appeals court steps in and says that no, the district court was wrong to dismiss it for that reasons, and sends it back to the district court.

4. Dominoes appeals to SCOTUS, saying "help, the appeals court got it wrong, please step in!" SCOTUS declines to get involved, so the case will go back to the district court, which may still find that the phone access provided is an adequate accommodation.

The SSN was never intended to be a secret. Nobody in 1938 thought that one day banks and other businesses would use it as a credential to establish identity.

"asshole"

Personally, I hate this Bowdlerization from the Times. It changes the meaning of the tweet, and it's not even the worst case where I've seen their desire for propriety interfere with their core mission of informing their readers about the world.

If their readers are uncomfortable with words like asshole, maybe a source like Time for Kids would be more appropriate for them.