Earlier this week, an article came out o …

Earlier this week, an article came out of some group that distilled the 25 “most dangerous” programming errors that are seen these days. (At least, I assume they only looked at ones that are still a problem, because I would say being able to shoot a bullet through memory is pretty dangerous, and it didn’t make the list.)

I skimmed the list when it first popped up on Slashdot, but reading Jeff Atwood’s comprehensive review of it at Coding Horror, I’m beginning to realize why so many of these things seem like obvious mistakes to me: they are the mistakes we keep hearing about on Security Now.

I guess I should write a letter to grc.com/feedback and thank them for making me a better programmer.