jayrhacker

Yeah, and sure he can pass a drug test if you consider:

LSD: 12 hour wash-out time for a blood test
Cocaine: 24 hour wash-out time for a blood test
MDMA: 24-36 hour wash-out time for a blood test
Ketamine: 24 hour wash-out time for a blood test, and it's easy to get a prescription for off-label use to treat depression

So basically, do all the drugs you want Friday night, by Monday morning you'll be clean enough for a blood test.

It helps to contextualize this work in the movement it was part of: Dada. After the invention of photography the fine arts community was dealing with a crisis: painting was the primary form of art, and painting was meant to capture reality faithfully. Photography turns that on it's head and we get the beginnings of modern art with the Ashcan school in 1900 which makes everyday life, including the lives of the less fortunate, an acceptable subject of painting (previously it was nearly all portraiture, landscape and scenes from history or fiction).

Less representative paintings give way to abstract art, and just 19 years later we see that artists are pushing the bounds of what is considered "art". Duchamp and company were asking the question of "what is art" with each new piece and the overall movement of Data and it's descendants such as Fluxus has investigated that boundary for more than 100 years.

if you compiled some code and then uncompiled it you would get the most efficient version of it ... ?

Sorta, an optimizing compiler will always trim dead code which isn't needed, but it will also do things that are more efficient but make the code harder to understand like unrolling loops. e.g. you might have some code that says "for numbers 1-100 call some function" the compiler can look at this and say "let's just go ahead and insert 100 calls to that function with the specific number" so instead of a small loop you'll see a big block of function calls almost the same.

Other optimizations will similarly obfuscate the original programmers intent, and thinks like assertions are meant to be optimized out in production code so those won't appear in the de-compiled version of the sources.

Historically, reverse proxies were invented to manage a large number of slow connections to application servers which were relatively resource intensive. If your application requires N bytes of memory per transaction then the time between the request coming in and the response going out could pin those bytes in memory, as the web server can't move ahead to the next request until the client confirms it got the whole page.

A reverse proxy can spool in requests from slow clients, when they are complete, then hand them off to the app servers on the backend, the response is generated and sent to the reverse proxy, which can slowly spool the response data out while the app server moves onto the next request.

ZFS will let you setup a RAID like set of small volumes which mirror one larger volume, it takes some setup, but that's the most "elegant" solution in that once it's configured you only need to touch it when you add a volume to the system and it's just a mounted filesystem that you use.

Does not solve the off-site problem, one fire and it's all gone.

For Science!

Under the heading: "Digital Signage Display"

Three Words: Digital Signage Display

Wow, in vehicle navigation in 1984 is pretty forward loooking.

This is a custom build for someone who wanted to have "the biggest pickup ever" for a few weeks before someone else on-ups them.

"we shouldn't let a few good apples exonerate the whole bushel"

You think someone would just do that? Just go on the internet and lie?