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.
Just mention in the ToC that this is a beta service and any claims of warranty or suitability for a given purpose, blah, blah, blah. Then just offer to release a patch once the exception can be reproduced and a suitable bug report has been filed.
I would expect they follow the model many other open source companies have done (deviations from this would probably raise at least one of my eyebrows): services and support.
I've run CM on most of my Android devices at some point. I stay with the vanilla carrier OS for a bit, but it inevitably starts to annoy me, and generally ceases to get updated after a year or two.
The dev community has done a terrific job of making it easy to root and install CM on a wide variety of phones, but everything still comes with massive "if you brick your phone, don't come cry to us" disclaimers all over it. This limits the user base to people that are comfortable hacking around on a command line and are okay with a small chance of owning a $200+ paper weight. Offering support contracts such that the average person doesn't have to dig around for hours on xdadev and cm forums trying to find information when they run into problems would expand their potential user base and be a welcome tool even for us hacker types. I know I've spent way too long trying to get S-off on my HTC One X. None of the wikis or forum posts have offered anything that helps resolve my specific issue. I'd gladly spend a bit of money to have a dedicated support person help debug it with me. Somebody who understands how the exploit works in detail and knows what and where to check to figure out why my phone in particular isn't working. I'm confident I'll eventually figure it out, but it's taking a lot more time than I'd rather spend on it.
They also currently provide premium services like an app that enables OTA updates to any CM rom, automated backup utilities for recovery, themes, launcher apps, etc. There's a lot of potential here for offering paid services that take advantage of your additional capabilities having an open phone.
I spent most of the time I was reading the summary trying to come up with some really clever/sarcastic/funny comment (Electrons spin faster! -- um, no that's lame. I got it, if you spin it backwards, it just says "Paul is dead" in a chipmunk voice.)
But then I got to this:
The team then used the minuscule forces of laser light to hold the sphere with the radiation pressure of light — rather like levitating a beach ball with a jet of water. They exploited the property of polarization of the laser light that changed as the light passed through the levitating sphere, exerting a small twist or torque.
That is so indescribably cool I just had to let that stand on its own. There is so much physics wrapped up in this one experiment.
I'll just leave it at an obligatory XKCD:
Science, it works bitches.
... the group of MBAs
- Flop sweating their asses of
- Furiously searching their email for that ass-covering memo where the IT guy said "Yeah, this should work"
- Wondering if there is enough coke on earth to get them through the rest of the day
For these guys, there are only two universal truths:
1) This is absolutely, positively, 100% the IT guy's fault
2) He can not fix this without the IT guy.
The impotent rage would be palpable.
It's not that caffeine causes us to die early, caffeine dilates time itself. We live a lifetime of productive bliss in only a few moments. Why else do non-coffee drinkers never appear to age? In what feels like 60 years for us, only a short time passes for them. They look younger because they are younger. But, they also live long enough to get Alzheimer's, Parkinson's, cancer. In a twist of irony our lives are shorter but our years are longer. We looked to the internet for the Singularity, but we should have looked inside. The Singularity is us.
Strike that, reverse it.
Epic fail. Only timothy or samzenpus are allowed to astroturf.
Finally a use for patents I can support. This will prevent anybody else from implementing this incredibly stupid idea.
And on a side note, if Google did get this to work would they be able to have the phone automatically call 911 if you were having a stroke?
I'll add in Boe Bots:
These are really simple to set up (especially if you're not really a hardware/circuits guy) and are a lot of fun to play with. Very limited processor, but that's not such a bad thing to start out. There's quite a lot of add on sensors/motors, etc, so you can accomplish quite a lot.
It's great for building path finding/obstacle avoision types of projects. If you take a liking to robotics though, you'll probably want to move into something more powerful pretty quick. But it is a nice cheap way to get some experience with the basics.