hesselink

Same in the Netherlands. Postcode and house number is unique and enough to deliver mail. I usually write the return address that way.

Does anyone else find this article unreadable? It sounds more like a marketing piece than an explanation of what merge queue is.

I was confused as well. I think (from some other comments) that the issue is that you can scroll to text that is specific to you and others might not have on their page (e.g. 'cancer' on some medical page) and then somehow gather from the requests that you scrolled there. It seems pretty hypothetical, but I can see the issue with forcing a scroll depending on what text is on the page, I guess.

And yet you provide none. What do you base this on?

It isn't, I don't understand where this comment comes from. You can derive the entire thing without writing a line of parsing code.

Haskell type classes by default pick the implementation based on a single type variable in its signature, but it can occur in multiple positions (including the return type). A commonly used language extension (multi parameter type classes) extends this to an arbitrary number of type variables.

The thing is, you're focusing on when you've detected that there is an issue (a crash). A lot of the issues with NULL are the fact that you can't easily detect if beforehand. It's not indicated in the types, or the syntax. That means that it's incredibly easy for a NULL issue to sneak into an uncommon branch or scenario, only to be hit in production.

Ctrl+V for making and operating on block selections.

Interesting, it doesn't seem to work here because my employer's VPN blocks the torrents.

I aliased 'g' to 'git'. Combined with git aliases ('st' for 'status' etc) this is almost as short but doesn't steal all the short names from your shell. So instead of 'gs' you have 'g st'. Upside is you save two letters even on uncommon git commands :)