thesnider

There are actually two different SRE roles: the one people are describing above where you are 85-99% of the way to SWE (Software Engineer), and you have sysadminy experience, and another one where you are 100+% of the SWE bar and optionally have sysadminy experience. The former is called SRE-SE (Systems Engineer), and the latter SRE-SWE.

SRE-SE interviews are super heavy on the sysadmin stuff usually, with less (but still significant) attention paid to SWE skills, whereas SRE-SWE interviews may not even have an SRE component (it's possible for candidates in the 'normal' SWE hiring pipeline to be shunted to SRE-SWE post-interview).

I think you're misreading that sentence. "Examples are the programming languages Clojure, which is a contemporary dialect of Lisp, Rebol and Refal.", which claims that Clojure is a dialect of lisp (indisputable), rather than Rebol. Rebol is just another example of a homoiconic language.

They would just fund the renter's legal team.

I wouldn't be so sure of that -- none of Google's clusters use ECC, for instance.

I don't think that optional typing is in general an attempt to solve sucky static type systems -- instead, many researchers and organizations view it as a way of converting programmers who have only seen Java into developers that willingly use the type checker. It's a great motivator when you experience a bug in production that the runtime helpfully reminds you could've been caught if only you'd turned on types in that code :).

This article badly wants a thing that already exists -- sandstorm.io.

Done.

If it's not 'too popular', it defaults to 'suggestions' mode, which will show all the vandalism -- switch to 'viewing' mode, and you'll only see the original doc.

Well, coal is still subsidized, so I wouldn't hold my breath.

Yes, if they're running NTP anyway. Normal clock drift/skew correction would already cause this sort of thing.

This is extremely dependent on your org, and is subject to approval from marketing.

It's change by 10X, typically.