Dangerous Code

At times coding can get dangerous, especially when you're pairing with someone. You know what I mean. Here's an example. You want to define a new method:

public void GetCount()

Forget the "l" in "public" and soon everyone is snickering. Forget the "o" in "GetCount" and you can have a potential HR disaster in the making. Make both mistakes and...oh, boy!

Anybody else know of coding disasters that could raise the HR klaxons?

* Posted at 05.19.2005 09:29:09 AM CST | Link *

Blog History