I agree with the above. Most developers turn exception handling into a god awful mess. In our shop, we have rules with regard to Java return values and exceptions:

1. A method should do one thing, and be named for exactly what it does or returns.
2. If the method is unable to successfully perform the one thing it's supposed to do, it must throw an exception.
3. Returning null is not an acceptable course for error situations within a method. Null values indicate non-existence of the return data the caller is seeking, not an error.
4. It is the caller's responsibility to determine whether it can safely continue if a method cannot complete its task successfully. If not, it must throw the exception upward, as it then cannot complete its own task successfully. This includes the entire program itself.
5. For methods that return a Collection, a null value should generally never be returned. The caller is seeking a Collection of something, so it's either empty or it's not.

Nothing profound here, but putting these together and articulating them has helped our staff to write better, more reliable code.

We are currently making little to no effort to verify eligibility to vote. OF COURSE there will be very few documented cases of fraud.

It's lazy to assume that your own sense of inferiority is actually someone else's supposed sense of superiority. If this weren't the case, you wouldn't give a second thought about someone else's reasons for choosing a particular platform.

Failed uploads do not constitute incorrectly filed or non-timely claims. The payers are not off the hook for them. This is especially true if the systems at fault are owned by the payer or its vendor. I have personally been involved with cases where delays due to technical issues delivering the claims caused payment penalties. If the provider's systems are at fault, that's a different story. In most cases, the claims are resubmitted by providers until paid, or their billing office intervenes and contacts the payer directly.

Actually, you don't know what you're talking about. Insurance companies pay claims based on contracts with their members and providers. I've worked with scores of insurance companies and every single one is trying to adjudicate and pay claims as fast as they can. Ignoring the claims does not release them of their obligation to pay according to the contract. In other words, the claim WILL be paid if they have contractual responsibility. It's just a matter of if it will be paid with penalties, lost discounts, and unhappy customers or not.

The additional issue with this breach is the exposure of medical data. Thousands of claims transactions were lifted. Claims contain identifying information (demographics), medical diagnosis data, medical procedure data, etc. That information can be used for blackmail and discrimination purposes.

I do hire developers, and I see brain teasers as a waste of time, meant to feed the ego of the interviewer rather than sort out people who are good fits for the company.

Communication skills are paramount in determining who has the best chance of success. That includes the ability to understand information being communicated to them, digest it, and respond by exporting that information clearly and appropriately based on an audience. It therefore follows that programming is every bit a communication skill as written, verbal, social, and listening skills are, and they are indeed correlated.

In my years of hiring experience, those with superior skills in the above categories make the best programmers. Even though we're all enamored with the idea of the asperger's guy in the corner who is a coding wizard, I've never come across anyone with poor written, verbal, social, and listening skills that could produce anything but garbage code. That may just be the programming/business environment we have, but it is still my experience and observation.

But getting back to the original question- we give candidates an hour-long programming test that is representative of the kind of work we do, weeds out those without basic skills, evaluates their coding decisions, and tests their ability to understand a business scenario and turn some requirements into reality. Brain teasers tell me none of this.

On a lighter note, you may or may not be surprised that over 50% of candidates who put "Java" on their resumes are unable to get past the first instruction to extend a given class. Completing this instruction concludes the first half of our technical test. Simply astounding.

I'm in the Twin Cities too. Check out KickAss VPS. They're served out of the Verispace colo center in Edina. I pay $25/month for an Ubuntu server with root access. Never had any problems.

Exactly. I think this commentary sums it up best: http://www.theonion.com/articles/i-cant-believe-the-tv-they-make-me-watch,10893/

Ahem. That's the preamble, and not an enforcable article of the Constitution.

Because it's not the government that provides us with that "wonderful developer world lifestyle". It's private enterprise like Amazon.

This is so moronic I don't know where to begin. How long have you worked in Healthcare IT? It's completely inaccurate to say that insurance companies are making ridiculous profits, and even if they were, who cares? Are you referring to any particular company? If so, which one? Are all types of health insurance companies making enormous profits, because I can tell you a lot of TPAs are losing business fast. Do you have any citations at all? All but the largest of insurance companies are struggling with compliance and investing in the American economy isn't the go-to solution. Try "investing in the Indian economy." Fixed that for you. I'm not making it up. It's not my personal theory. I work in the industry and see Americans lose their jobs every day due to cost pressures resulting from ill-conceived regulation. I don't disagree that the new code system will be beneficial, but the government took a disruptive approach in rolling it out.

Astoundingly inaccurate. The thing that people don't understand is that ICD-10 is not really an IT problem but an administration problem. Insurance companies must entirely redesign their benefit plans around the new code systems AND maintain payment neutrality at the same time, AND support dual code sets. Their adjudication platform vendors will be charging them massive amounts to upgrade and convert, not to mention their own resources. And when things go to hell, IT will be blamed because managers assumed that a one-to-one crosswalk was all that needed to be implemented. The cost of the conversion will be enormous for EVERYONE, and I predict the compliance deadline will be extended as a result.

So. Much. Anger. Does it ever get tiring being a liberal? It seems the amount of hateful anger necessary would just drain a person. Anyway, we conservatives see through terms like "reich-wing." It's a way for liberals to attack those with whom the disagree without actually going to the trouble of making a cogent argument. "Racist/poor-hating is as racist/poor-hating does" Here we see the main fallacy with liberal logic. They often redefine concepts in order to villify their opponents. For example, opposition to affirmative-action policies is most certainly "racism" to the liberal mind. No, racism is believing that someone is inherently inferior based soley on their race. Nothing more. From the proposition, "If someone is racist, they will oppose this policy" liberals immediately derive the reverse- "If someone opposes this policy, they are a racist." This assumption cannot be made, as any student of propositional logic will tell you. So no doubt your next response will be a stream of obscenities, or STFU's or whatever. Maybe you'll become so angry your head will explode. Who knows. I'm done with this thread.