If someone steals your computer, its still encrypted, assuming you've password protected your private key..

So what happens if you lose the encrytion keys in a crash?

You make it sound like being a contracter is a bad thing. Me and some of my friends are all independend contractors: We like it much better then actually working at those companies. We are treated with respect, are payed for overtime, and are our 'own boss'.
The difference in knowledge is stunning: The bigger the company, the more IT people they have, and the less they get done. Some of my friends are able to replace 5 'normal workers', that are of the kind that only have papers and zero actual knowledge.
Btw we're all in the unix, linux and storage business.

..gets a lot easier if you DONT care about people little problems and annoying secrets at all.

That was the same reasoning albert einstein used for creating the a-bomb

i was amazed by that as well

Can't view that video on my android: *Your mobile device may not support H.264 video playback*

What if you somehow alternate the ir beam, so they're not on at the same time?

...by apple, microsoft or oracle, claiming to have some broad patent on multitouch and/or gestures?

After reading http://yro.slashdot.org/article.pl?sid=10/08/17/0437242 i'm affraid no big company can make anything innovative, without risking a patent lawsuit.

Nobody mentioned rob gongrijps cryptophone yet. It uses regular cellphone calls. Instead of voip. You both need to have that phone tough.

The force is strong in this one, it is!

sorry about the bad formatting, this time in plain old text:

I recognize this to, altough i do get enough sleep and spend time doing other stuff.

I usually try to work until i reach a good "stopping point". e.g. a (couple) of bugs solved, a new feature ready, etc. This way its easier to take your mind of it and get some rest.

If you dont do that, the problems you describe do occur: you keep on going because everything goes well and smooth, and its fun. But after a couple of days you get tired, sick , exhausted, have trouble sleeping, dream about code etc. At this point you get inproductive and make mistakes, or even have to take a day or 2 'rest' to 'recover'.

Especially dreaming about code is bad, you have to prevent that, by stopping a hour or 2 earlier, and do other non-computer related stuff. Otherwise your brain wont rest enough and the same problems might reoccur.

Some tips:
-whenever you need a short break or are compiling, clean up your house and do the other 'dumb' stuff you normally dont do. This way you move and stuff gets done. Just cleanup a few things at a time.
-dont go to bed right after coding, build in some relaxing time.
-try to stop at a good point so your mind doesnt have any problem left it wants to solve: this means sometimes you work longer, but sometimes you work SHORTER and DONT start working on a new problem. very important: once you started a new problem, its too late and you're locked in ;)
-what also helps a lot is meditation: but you have to take time for it and have to ease into it. Its not something you should schedule and rush. :)
-if you work together with someone, get together at least once a week when the weather is nice, and take a walk, talking about work, code, or other stuff.
-try to do meetings you have with 1 or 2 persons outside while walking or sitting outside somewhere.

But its true: its always hard to keep the right balance between coding and 'the rest'. :) I'm always had this problem a bit, nice to see i'm not the only one.

Someone else has any tips like these?

I recognize this to, altough i do get enough sleep and spend time doing other stuff. I usually try to work until i reach a good "stopping point". e.g. a (couple) of bugs solved, a new feature ready, etc. This way its easier to take your mind of it and get some rest. If you dont do that, the problems you describe do occur: you keep on going because everything goes well and smooth, and its fun. But after a couple of days you get tired, sick , exhausted, have trouble sleeping, dream about code etc. At this point you get inproductive and make mistakes, or even have to take a day or 2 'rest' to 'recover'. Especially dreaming about code is bad, you have to prevent that, by stopping a hour or 2 earlier, and do other non-computer related stuff. Otherwise your brain wont rest enough and the same problems might reoccur. Some tips: -whenever you need a short break or are compiling, clean up your house and do the other 'dumb' stuff you normally dont do. This way you move and stuff gets done. Just cleanup a few things at a time. -dont go to bed right after coding, build in some relaxing time. -try to stop at a good point so your mind doesnt have any problem left it wants to solve: this means sometimes you work longer, but sometimes you work SHORTER and DONT start working on a new problem. very important: once you started a new problem, its too late and you're locked in ;) -what also helps a lot is meditation: but you have to take time for it and have to ease into it. Its not something you should schedule and rush. :) -if you work together with someone, get together at least once a week when the weather is nice, and take a walk, talking about work, code, or other stuff. -try to do meetings you have with 1 or 2 persons outside while walking or sitting outside somewhere. But its true: its always hard to keep the right balance between coding and 'the rest'. :) I'm always had this problem a bit, nice to see i'm not the only one. Someone else has any tips like these?