and what sucks more is that these stories still exist in the timeline the day after.
I took yesterday off from
Yeah - I took the day off from
So many were incomprehensible - it was apparent there wasn't any real news yesterday.
Yes - I was thinking something similar.
Backstory - his wife recently left him and took the car.
"Dear Slashdot - help me find a car that belongs to my employer"
I'll reply to this in just a minute. I'm still typing my 1,000 character
oh wait - you already stole it from Adobe? damn.
Please wait while I create a new password, "Zza"
that'll keep you busy 'cause you probably start at 8 character guessing.
I thought about that the other day. Not having plan B in their back pocket? All shows must come to an end - whether it be retirement or "ran long enough."
This is like not having a second datacenter - and no backup tape. Shit out of business.
but their creed (or motto?) was "if somebody dies, leave them behind"
Whether it be a car breaking down or somebody actually dead - they once said (several years back) that they had all sworn to keep going !!
However - Jeremy was kind of the leader. Hammond maybe could do it - would be strange. If it were me - I'd bail because I'd just "cock it up." Wouldn't want to be around as it fell down. Get out while on the top.
I saw an interview yesterday with Capt Slow on his front porch. He acknowledged the media reports and then said "If you'll excuse me I have a LaFerrari to list on eBay" and left.
Yes thank you. This is a classic mistake that many first time programmers make. Years ago somebody was comparing the speed of C++ over VBScript/IIS over Java for writing Web pages back to a browser. They too came to a similar conclusion - and also made the same mistake.
When writing to disk - the data is written once. The algorithm for in memory is not doing the same thing. It is allocating a new buffer - copying all data to said new buffer - and finally adding data to the end. If one compared the I/O of the two program executions the "in-memory" version would have many times MORE I/O.
Doing this:
Loop N.{ x = x + newValue}
Write(x)
Will always be slower than
Loop N.{ Write(newValue) }
In C# and I think Java - there is an object called StringBuffer - and is intended for this kind of workload. The first thing I learned in data structures class was how to expand buffers using different algorithms and pro/con of each (heap design for instance, buddy system).
Plus - O(n) is not created equal.
You forgot to carry the "psychology" in the 3rd equation. We all know the basic formula - Less In, More Out.
I have to run - that bag of potato chips is talking to me and I need to eat them to shut them up.
There are whole TV shows written around this very idea. One can simply observe mannerisms and jump to fully detailed truths about people. These writers must have something to base these plots lines on - they couldn't publish a TV show if it weren't true
So why shouldn't a TSA executive use the idea, sort out the details, get the best scientists/consultants to provide the truthiness, and create the real thing. I mean - isn't this what the Lone Gunmen proposed in X-Files? Secret science that was all true but hidden from us normal folks via conspiracy theories?!
Junk Science is labeled by people who refuse to think outside the box. Go talk to the Creationists - they know what's going on.
"The one charm of marriage is that it makes a life of deception a neccessity." - Oscar Wilde
