terminado

It's like stumbling into elevator after elevator, while running the hundred yard dash at top speed, everywhere you go, only to encounter the perfect dance partner to fall in love with at first sight.

You have to trust those prescribing it, which, if you don't trust the advice of a doctor with a needle, would you trust them with a brain scan that labels your child defective, before they can even talk?

Some people (those who might consider skipping vaccinations) might avoid such an exam entirely, and choose to wait until their child is age 10 or 15, to decide whether they have some sort of problem with their social skills, or worse.

Even with millimeter-scale components, I'd still think dust and debris could be a real problem. Is it just that 12 hour runs are short enough to just accept an imperfect production output, since it's a personal project, or is dust not as big a deal at this scale as I'd imagine?

https://en.wikipedia.org/wiki/Robert_Morris_(cryptographer)

I have no proof of this, but through oral tradition, such a tale has been relayed to me. Believe whatever you will.

  - Artificial Intelligence
  - Machine Learning
  - Neural Networks
  - Blockchain

It's better than presumptively assuming that "Science" is an infallible always black-and-white.

In the cold, dry air of winter your breath vents upward, but getting near sunny 90 degree weather, during summer time, it might descend and pool at the feet of gatherings of people at barbecues.

Carbon dioxide in ambient, matched temperature mixtures tends to be dense, and sinks toward the floor in many conditions (similarly true for carbon monoxide), but local conditions obviously vary, and odor travels differently than entire air masses. If mosquitos are already out, they probably travel along the odor gradient, toward the most concentrated area of scent.

It leaves no room for externalities and circumstance, and assumes the individual had all needs met, perfectly, at all times.

Facts are facts, even if someone came up short once or twice. Maybe blame is irrelevant, and excuses aren't a substitute for productivity, but simply put, that's not how you measure humans, and any human knows that.

  “More often than not, she relies on charts, graphs 
   and quantitative analysis as a foundation for a 
   decision, particularly when it comes to evaluating 
   people … At a recent personnel meeting, she homes in 
   on grade-point averages and SAT scores to narrow a 
   list of candidates, many having graduated from Ivy 
   League schools, … One candidate got a C in macroeconomics. 

  “That’s troubling to me,” Ms. Mayer says. 
  “Good students are good at all things.”

This sort of program probably crosses over into PERFECT CITIZEN territory. [0,1]

[0] https://www.wsj.com/articles/SB10001424052748704545004575352...

[1] https://twitter.com/treekisser/status/286555593307742208 (paywall/seo referrer hack)

The corollary is 30 ton tractor trailer changing lanes on the highway, and concluding that there's no traffic because it would prefer not to see it.

Censoring the rear view mirrors is a bad idea no matter how much you hate what you see in them.

  ...with just 500 likes the social network can 
  insinuate more of your personality than your 
  lover.

There's no clear demarcation between devising a convenient contraption, versus implementing an inadvisable hack that leads to a hazardous outcome, especially within the scope of web based systems, since no portion of the internet is to be regarded as reliable life-saving infrastructure.

I think the mistake is to trust packet-switched networks and peer-oriented protocols as reliable systems at all.

If you cannot control the whole system, end-to-end, and any unwitting peer can over-consume bandwidth (jamming traffic and communication with interference), effectively cutting you off from a necessity, why would you bet your life on the availability of that system?

So, to look at the words:

  The notion that software engineers are not 
  responsible for things that go wrong will be 
  put to rest for good.

  The notion that *some* software engineers *cannot*
  be found as responsible (in part or in whole)
  for *some* things that go wrong will be 
  put to rest in *some* situations.

Meanwhile, there is very obviously a line to be drawn between the programmer that programs their VCR clock to time a recording, the programmer that programmed the VCR as a consumer-grade product intended for purchase by unlicensed individuals, the TV network that broadcast the television show at the time the individual programmed their VCR to record 60 minutes of broadcast on a given channel, and the programmer who locked me out of the firmware on my smart phone.

It's hard to avoid prefacing a question like that as a matter of scientific interest, without including a disclaimer that thinking about harming whales is kind of terrible.

Electrocuting whales is something a super villain might try, so you kind of have to play into that aspect of the premise. Figure it's an otherwise regrettable question he didn't want to just shy away from.

But it's not enough to just be better than the cotton candy fluff of recent movies, since that's not a real competition. It's a solid movie that stands on its own, even despite some quirky flaws in the delivery and editing of the performances.

It's not Rocky Horror Picture Show, where you and your friends have a party, and participate. It's more of a sleepy, quiet time movie like Taxi Driver. Like Taxi Driver, and any other classic movie, it gets better with repeated viewing, as more details tie together.

It's not a mind blowing movie, but for it's time, it dealt with a lot of new themes in extremely subtle ways, without excessive treatment. The future was cast as a recognizable, ordinary reality, taking on a tone that really only draws a cult following, but warrants substantial appreciation.

Movies like this don't get made anymore because risking a budget on cult appreciation doesn't land well in a pitch, especially amid the modern environment of implicit piracy, if it's fair to label shared viewing as such.

Whether it was the first movie to feel vaguely cyberpunk-ish or not, doesn't matter much anymore, but Blade Runner had a deep gravitational pull that influenced visual concepts of the near future well into the late nineties.

Without a sequel, all of the open-ended background trivia that was never elaborated upon, left open a whole universe to imagine, and this is where the cultural resonance ties in. The people who enjoyed the movie were left free to speculate about what really went on in the off world colonies, given the curiousities revealed by film.

I wish more movies were like Blade Runner. It's a rare item. It's not a movie you watch once. It's not a blockbuster. It's not a movie you turn off, when it finds it's way onto your TV, however that manages to happen.

The worst part about the movie is Roy Scheider's fatherly internal monologue narration, which tediously explains-like-i'm-five for half the movie.

So maybe that gives us a hint, about what Clark's narration would have done to 2001.

That little sound bite also chimes in over and over again, sounding forced, poorly performed and with a corny distortion effect layered on top, in some presumptive attempt to resonate an idea with the audience. Maybe to remind you once more that the movie is supposed to be a sequel, despite an almost total discontinuity with 2001.

It draws a lot of parallels with Stephen King and The Shining, which had provoked Stephen King to exert more creative control over movie adaptations, often with laughable (or maybe unintentionally comedic) b-movie results.

And you didn't even condense the salient detail for us, being that Kubrick had cut Clark's extensive voice-over narration, which wasn't revealed until the premiere, provoking Clark to walk out of the screening.

  Dave, although you took very thorough precautions in 
  the pod against my hearing you, I could see your lips 
  move.

  It seems unlikely[...]

  the energy effects of a 6.5 mm round at range 

  those of a 5.56 mm round point blank

The head wouldn't be ripped clean off. It wasn't a 12 gauge shotgun inside the mouth. These weren't explosive shells. They were ball rounds.

There's a better write-up, which escapes me at the moment, which clarifies the smoking gun of Java's painful slow performance under certain circumstances as rooted in L2 cache churn, due to the deadly combination of the java.lang.String class' immutability in memory, and all java.lang.Object instance references (literally everything, including the references themselves) being passed around as messages which are... you guessed it, Strings.

This is why a GUI on a Desktop java runtime environment feels slow (no one cares about your Swing app, and go out and buy four times more RAM (64GB maybe? oh, why not?) just for your IDE), but server processes, while also memory-hungry, are capable of reasonable performance in exchange for marginal code readability (even if verbose), when processing mostly primitives, threaded in parallel (yay, stateless protocols!), and packed into highly normalized formats serialized as JSON data structures, or XML/HTML DOMs, handled by proven libraries with good API's.

People make so much hay about the curious non-locality and uncertainty of spin, and tend to get tunnel vision about how nothing makes sense anymore, leaving out the broader strokes which have pretty reasonable underlying principles.

https://youtu.be/7UR6epdce-o?t=40

Disposable cartridge consisting of briefly outlined carbon nanotube component...

How does a regular person make one of these nanotube cartirdges?