Looks like the website is done with it: https://undefined-medium.com/

In the article, the author explains that from the cyclists orientation, the car approaches from 94 degrees.

Doesn't matter. If you're cycling and you see a moving car, assume the driver doesn't see you. Never cross the path of a moving car even if you have the right of way or a green light etc. When you approach a junction, your head needs to be on a swivel constantly looking left and right and you need to be prepared to stop even if you have the right of way. This pretty much goes for motorcyclists as well.

I'm not blaming the cyclists here, but the reality is that when you are cycling it doesn't matter whose fault it is if a car hits you. You're still dead.

If you read the article, then you'd know that the cyclist probably did not see the car at all.

The cyclist may not see the car if they stare blindly into the distance in front of them. GP is making the point that the cyclist should be aware of their surroundings, and taking precautions accordingly. This includes looking for approaching traffic down the length of a side road on approach to an intersection.

While I don't discount that there may be freak scenarios, as a motorcyclist I agree. If I don't see a car, a pedestrian, a bird, a kangaroo, a log on the road, I go to hospital. It's as much my responsibility to ensure my own safety as anyone else's.

The rule I generally follow as a pedestrian is that the object with greater linear momentum has the right of way.

You can get a stainless steel french press. Typically they are vacuum insulated as well, which is nice.

Gorgeous. Anyone have any tips on printing this in high quality?

Had the same thought. See my comment elsewhere in the thread. Turns out that the USGS sells posters.

I know a professional printer who prints my maps (http://www.wellingtonstravel.com) and is really good quality. Or you can find a local printer who can help.

Actually collapsing comments helps. Often insightful top level comments are posted at a later time. These remain less read and less voted because of their position.

Interesting that he advocates MySQL. PostgreSQL can index and interact with the JSON stored in it's columns, which make it a better choice as a NoSQL replacement.

http://www.postgresql.org/docs/9.4/static/datatype-json.html

I believe that MySQL 5.7 comes with JSON data types too.

https://dev.mysql.com/doc/refman/5.7/en/json.html

Indeed. To expand a little: it has a Json type, functions & virtual columns.

So you can extract part of a Json document and index it. The optimizer can also match Json expressions to indexes

The JSON datatype is only useful if you want to query on the blob, which is not the case in Wix's case.

But you tell to keep columns that need indexs outside of the JSON so you can query on them, which is not necessary with Postgres

It also provides validation and is often more space efficient :) the internal format also technically supports partial update, but that is not yet a supported feature. So I wouldn't suggest using text if you are not querying.

You can query on individual fields with the jsonb type

Actually they frequently have member sales with insane prices.

You missed the joke re: Go 2.

I don't think Go is done. The active development speaks otherwise.

I think everyone missed it. Glad you, at least, didn't :-)

  Location: Los Angeles, California and Edmonton, Canada
  Remote: Yes, preferred
  Willing to relocate: Yes, if the location is cool enough.
  Technologies: Go (Golang)
  Resume: http://goodcoffee.ca/hn-jonah-resume-pu2c6cas7tcwjqj9/
  Email: Jonah at GoodCoffee.ca

I've been writing code for decades and am currently looking for a remote position coding go. As an example of my go code, see https://github.com/JonahBraun/wago I am actively working on the next release, expecting to be done next week.

I think you posted this because pasting the OP results in a syntax error. The problem is actually the list in the compound command needs to be terminated with a newline or semicolon. Both of the following are equivalent correct oneliners:

clip() { [ -t 0 ] && pbpaste || pbcopy;}

function clip { [ -t 0 ] && pbpaste || pbcopy;}