tuke

The post suggests that "freight trains have priority."

By law, passenger travel is expected to have "precedence."

Read: https://www.amtrak.com/content/dam/projects/dotcom/english/p...

No comment along the lines of: "ew, Python."

Nice. The embedded querying is neat.

I see the query language goes: `select ... from`

One thing I like about query languages that start with the "from" class is that then it's easier in REPLs to provide suggestions for what can be selected.

You type, say, `from people` and you can get a suggestion for `name`.

One thing I like to do is try to get all stories to be (approximately / more or less) the same size.

I.e., split and gather work so that you don't need to score them. Then you can still get some rough feel for capacity without the bother of sizing.

And if you do this, you shouldn't split hairs and be dogmatic.

It is worth noting that Scrum, for one, does not require (or even recommend, at least according to the latest Scrum Guide) story estimating or pointing.

I would agree that in practice all of those anti-patterns related to story estimating/pointing can work against the values of the Agile Manifesto.

What is Facebook?

This has bugged me for a long time.

My company complies with HITRUST. Many of the HITRUST controls are syntheses of controls found in NIST, ISO, and other organizations.

In some cases, I want to know where a HITRUST control comes from: But since I can't look at ISO without paying, I am blocked from understanding the provenance of some HITRUST controls.

I don't like that.

Nice.

Are the things under "Things I've changed my mind on" things you believe now, or have stopped believing?

(Can't tell which way the change of mind is.)

$8k/mo revenue is great, but what's the profit?

Need to add Ann Wollrath to this list. (Primary author of the RMI whitepaper.)

No! How could that be?

True

Weird how the report itself doesn't have a date.

Frankly, this one patent is worth a lot of money. This is the magic by which Looker casts out duplicate records in joins.

http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=H...

I knew Amazon was powerful, but didn't know they had the authority to raise the minimum wage "for all U.S. workers." Wow. Incredible. Other companies can only raise the wage for their own employees.

I'm just impressed to see the name Niklas Luhmann in HN. Well played.

This is fine as an opinion piece and a close reading of parts of the scrum guide, but some kind of evidence (even reports via surveys) would help.

Yes, doctors should focus on the patient and the family, not the computer. Technology should be scrutinized to be more supportive.

Yet a significant problem with this article is that it provides no comparison to other professions.

"A clinician will make roughly 4,000 keyboard clicks during a busy 10-hour emergency-room shift" -- I doubt that 4,000 "keyboard clicks" is unusual for any profession at present, even one where attention is moving across interactions with patients, colleagues, machines, and the computer. A page of text is about 3,000 characters.

(Aside: I'm actually not quite sure what is meant by a "keyboard click" is -- maybe the author is talking about mouse clicks or toggling checkboxes; elsewhere in the article the phrase is "4,000-key-clicks-a-day" -- if it's just 4,000 taps to keyboard keys, that's a pretty low number. I don't think that 4,000 checkbox or mouse clicks is even really such a big number. Answers here (https://www.quora.com/What-is-the-avarage-number-of-mouse-cl...) suggest between 5000 and 7000 mouse clicks/day. Another resources says a doc does about 2500 clicks/day -- http://www.healthcareitnews.com/infographic/infographic-one-... -- and that's for a 16 hour shift.)

In any case, is there something distinct about clinician work with regard to the use of computers, compared to what we're all doing? A claim that there is would strike me as special pleading. If there is an argument to be made, it must be made comparatively.

The author also claims that "Even if the E.H.R. is not the sole cause of what ails us, believe me, it has become the symbol of burnout" -- do doctors _really_ suffer from more burnout than other professions? _Doctor-authored_ studies may say so, but we need to have unbiased studies of burnout across the professions, and understand generally how being lassoed to a computer affects morale.

I would strongly advise that we read carefully the language for Art. 3, "Territorial scope," which says:

  (2) This Regulation applies to the processing of personal data
  of data subjects who are in the Union by a controller or processor
  not established in the Union, where the processing activities
  are related to:

    (a) the offering of goods or services, irrespective of whether
    a payment of the data subject is required, to such data subjects
    in the Union; or

    (b) the monitoring of their behaviour as far as their behaviour
    takes place within the Union.

So, I would ask: Has HN made an "offering of goods or services . . . to such data subjects in the Union"? (https://gdpr-info.eu/art-3-gdpr/)

The critical issue is that word: "offering."

The language here seems to be about intentions. Has HN "offered" anything to data subjects in the Union? Maybe not. To be sure, people in the EU may have chosen to look at HN, but has HN sought to "offer" to them?

(The presence of a domain such as news.ycombinator.eu would tip to "yes.")

I use Gollum (https://github.com/gollum/gollum) which is the engine for Github's wikis.

It used to be harder to stand it up for personal use, but now it's quite easy.

I write my notes in Markdown, and have fenced code blocks. It provides search. You can do diffs.

N.b., unless things have changed, I don't think Dyn (for one) allows secondary DNS. Maybe that has changed. {?}

The patient would presumably consent first (to the notification emails).

True enough, but there are also companies that were designed from the beginning to have vertical integration and control much of their business from beans to buildings. And of course I am thinking of Starbucks. (People don't really understand the technological story of Starbucks, which has a lot to do with their introduction of the vacuum packs to get their coffee across the country, and overcoming the challenge of brewing coffee on passenger jets.) Mostly for the better, they decided long ago to own as much of the stack as they could.