Unless you bought the phone outright, or brought it with you, a contract normally means the /provider/ owns the phone until the contract is up. You'll be paying off the phone as you go, and until its paid off, you dont own it, so theoretically the provider can do whatever they want to /their/ phone.

Start making lots of mistakes to prove your point. :-) I personally find that sometimes, when the right song or songs are on, I get into a groove and do much more work. As for accuracy, its probably about the same. Music more so helps with my productivity.

I too have also secured a job after explaining to my new employer that I left my previous employer due to "things that were happening that shouldnt be, and things that werent happening that should have been." That was the extent of it, I didnt go into detail, but it didnt seem to have any negative impact on my prospects. They hired me for my experience rather than whether I had anything good to say about my previous employer or not.

What the hell did he just say?

I went for a haircut yesterday, this particular barber charges $25/cut. While I was waiting 3 people had their hair cut (thats including of the person already in the chair when I walked in), and another 2 people came in to be served after me. Thats $150 for maybe 1.5 hours work? Moral: become a barber. Seems to be pretty good money, and despite this "financial downturn" etc peoples hair still grows and needs to be cut...

Filtering the path would not have prevented this from happening. However, filtering paths whos length was unrealistically long would have done a world of good.

Most already do. The problem was not the ASPATH itself, it was the length of it. The routers affected did not handle updates for a prefix which required more than one AS_SEQUENCE segments in order to obtain the full AS path. The existence of the additional AS_SEQUENCE segment is what triggered the bug, causing the receiving router to treat the update as invalid, and the BGP session is dropped.