OPC (Other Peoples Code) Column

This issue’s topic was about dealing with OPC (Other Peoples Code) as a consultant.  It’s a difficult thing, sometimes, to say no to a potential client based on your first (and sometimes second) look at their code.  While I always regret saying no to paying work I’m always helpfully reminded by my wife why it’s a good idea NOT to take some work.  She does, after all, have to listen to be complain about it!

I’ve certainly learned a few habits over the years by trying to decipher someone else’s code.  Naming conventions are the number one problem I see with most OPC projects that I see come my way and I spend a fair amount of time deciphering what the name of the controls and variables *should* be.

What about you?  What horror stories can you share?