Carries can save money by having less towers but by using higher transmit power. I have heard that this can show up as the phone reporting full bars, but not being able to initiate/receive calls due to insufficient transmit power in the phone.
While possible, that doesn't seem likely. Doesn't the phone have to do some sort of handshake with the tower to even show the bars? Or are you saying that the phone only has enough power to do the handshake?
My understanding is that when the phone is idle, bars are commonly measured based only on the quality and strength of the incoming signal. The outgoing signal might be stable enough for a handshake but not for a call.
Of course the other possible explanation for full bars but no calls is that the network is busy.
I think the writer was talking about communication skills instead of country of origin.
At least I would think twice before applying again to a company, that hasn't previously answered my job applications in due time, so I definitely agree with the writer on that one.
. . . except that doesn't get you a modifiable list, it just wraps a List interface around the array that's implicitly created by the var-arg, so it's a trick you have to be careful with.
Personally I often end up writing little helpers like:
List<T> list(T... args) {
return new ArrayList<T>(Arrays.asList(args))
}
usually in test code. A built-in List and Map-initialization syntax is really something every decent programming language ought to have.
(Consider using the Google collections library if possible. It already has that in the form of classes like Lists, Maps, etc that provide builders and factory methods.)
