The leveling has little to do with money or infrastructure and everything to do with the composition of the population.

The per-capita mileage has leveled because we have a lower percentage of people in the younger, more mobile age groups. The baby boomers are reaching an age where they stay home more than in the past. The less-populous generations behind them are still working, traveling, driving as much as ever... there are just LESS of them as a PERCENTAGE of the population.

I never said anything about "fly through the air". My post said thrown back or bruised, I suppose thrown back could be interpreted to mean flying through the air. That was not the intent in my statement, so let me rephrase: "Then you could survive being shot and also continue to return fire without being as easily knocked off balance, spun, or badly bruised."

Maybe if you are wearing full Level IV body armor. Most of the lighter stuff traditionally worn by law enforcement still imparts a great deal of impact to the body, especially with higher mass or higher velocity rounds.

Place this behind an existing body armor compound (one that stops the bullet) and use the foam to absorb the remaining shock. Then you could survive being shot and also continue to return fire without being thrown back or suffering bad bruising.

They claimed that the Google Support forums were being swamped with complaints. However, a simple search shows that "swamped" apparently means a couple hundred topics, only a few of which are related to service issues (most seem to deal with rate plan questions, upgrade questions, or how to order questions):

http://www.google.com/support/forum/p/Google+Mobile/label?lid=18bf75ad33b7d554&hl=en

Nope, she doesn't have long nails. She thinks it may be because her hands are usually cold, though I'm not convinced. She does use moisturizing lotion and hand sanitizer fairly often, which I think that is a more likely cause for poor conduction.

Ah, I see that now, I haven't updated my iPhone since mid-August... it will be nice to finally have MMS... but the 3G (battery/coverage) issues and AT&T's network (though some analysts say it is the iPhone hardware) will still drive me to a different phone.

Their definition seems pretty broad, basically any phone that can run any of the smartphone OSs. More interesting is that the iPhone's main competitor, the W-Zero3, was built and released in 2005, 2 years before the iPhone American release in 2007 and 3 years before the Japanese release. The W-Zero3 has equal or better features with the exception of a touchscreen. So the iPhone is winning the market in Japan based upon marketing and the interface.

I own an iPhone. I am definitely moving away from it as soon as my contract expires... a few reasons: 1) horrible battery life with 3G usage, 2) lack of MMS, and 3) AT&T's network is sub-standard (I experience 2-3 dropped calls every day).

Interestingly, my wife refuses to use any iPhone, since the touchscreen never responds accurately to her touch. Most of her friends have similar issues, and now that I think about it, I don't see many women using an iPhone.

SMB2 is not required, it can be disabled.

From an Administrative prompt issue the follow:

"net stop mrxsmb20"

To make the change permanent, also issue:

"sc config lanmanworkstation depend= bowser/mrxsmb10/nsi"
"sc config mrxsmb20 start= disabled"

Seriously, why is everyone getting so bent over something that is a three-line permanent fix?

I like your method. Put them in a situation that relates to the job you expect them to do.

I have been employed by three companies in the past 22 years. Each time I moved on, I left on good terms with my current employer and listed my previous boss on my resume as a reference. In my current position, I do the technical interviews, generally over the phone or a lunch meeting. I usually prepare for the meeting by contacting the listed references and asking them about the applicant. If someone lists three college buddies, or three junior coworkers, or three people from completely non-related fields, then I have a pretty good indicator already that they were not respected by management or senior developers in their last job. I find a loose correlation between the quality of the references and the quality of the applicant.

In my interviews, I generally give a simple requirement and ask how they would solve it. I don't care if they know the details to implementing the latest and greatest algorithms or programming methods. I care how they approach the problem, what questions they ask, and how they think through the solution. Also, within ~10 minutes of questioning, you can determine if the applicant really knows programming or just knows buzzwords and for loops (and if you can't, then perhaps you are the one who just knows buzzwords.)

Talking to and assessing references can give you a good indication of work ethic and behavior.

Talking to and assessing the applicant can give you a good indication of knowledge and talent.

Between the two, I've been very successful in hiring quality developers for our company.

So then do it. Create the test and give us the results, let us verify your test methodology and your data and your results. Until such a time, ID is merely conjecture and not a scientific hypothesis.

As others have said, learn the concepts.

You should also find a class that requires group programming. Learn how to interact with fellow programmers, how to operate within a team environment, and how to document your thoughts and processes. I've found that social skills are very valuable in any organization.

Exhale fat? Great... now I'll have to worry about someone breathing second hand fat in my face...

FTA:
"By July 10, 2009, the Plaintiffs shall provide the Defendant with yearly estimates, beginning in 1999, of the revenues generated by their copyrights in the specific songs for which they intend to prove infringement at trial. They should separate physical and digital music sales and should provide Defendant with a description of the methodology used to arrive at these figures."

Tax returns would not contain revenue information for each individual song.

[copied from another reply to a comment about it being grayscale]