My TV just started playing Breaking Bad on Netflix...
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
And Perl code!
Not looking forward to the selfies...
Studies have shown...
Studies have shown that when people say that, the vast majority of the time they are saying some bullshit thing they made up and then appealing to a false authority to lend it credibility.
I'm guessing a minor mental error.
10000/365/8 = 3.4, but very very few people ever work 8 hours a day, every day of the year with no time off.
Except for moms. *high five*
I tried viewing this site from my work, and the map was replaced by my corporate 'Ad Blocked' image.
Perl Traumatic Stress Disorder
My thanks to this young man for his sacrifice, from a fellow perl hacker who's spent 15 years in the trenches...
you could be a chatbot, whreas I know I am definitely no
That sounds like something a chatbot would say. Nice try, Carp.
It's still clean energy. Humans are carbon-neutral.
If you run out the time axis long enough, you'll see it more reflects a bathtub curve than 1/x. I.e., in a long enough relationship, there will inevitably be a dramatic rise in posting frequency. Usually this is an indicator of a pending failure. When you see the onset of this increase, it's best to implement some redundancy. It may accelerate the failure of the first component, but ensures no disruption in service.
Wear a tshirt with a message written in a carefully formatted font so it causes a buffer overflow, giving your tshirt root privileges.
Mine would have the decss code on it, so the drone starts shooting pirated DVDs at everybody. The RIAA will make short work of the problem at that point.
What a bunch of crap. Everybody knows Co-60 is a deflationary currency. If you hold it, half of it will be nothing but nickels in about 5 years (Ni-60 to be exact). Oh, and you'll be dead.
Their password is usually just 'friend' in elvish...
Most engineers follow UDP protocol. Spewing a bunch of packets into the ether. In light traffic, this isn't a big problem. Plenty of bandwidth and sufficiently capable endpoints that they can reconstruct missing packets, or at least identify when they're missing something. However as traffic increases, packet loss can reach intolerable levels and communication breaks down entirely. If the engineer doesn't adjust to the network load, they can have an adverse effect on the entire network performance. In extreme cases the network admin (your boss) may need to remove the offending device from the network altogether.
They'd be better served to use TCP. Establish a connection. Send information in well defined packets. Confirm receipt. Re-transmit if necessary. Yes, it's slower and more overhead, but reliable information transfer is a must in a robust and useful network.
Oh, and always ACK with a smile
Ditto, and mine is convinced it is crossing the Alps, given where my wife usually sets the temp.