• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

"How to write unmaintainable code"

I don't get it. This seems like pretty common-sense stuff, all in all. In fact, I think a lot of this comes right out of my own handbook.
 
hahaha amusing... about 50% of the stuff in there I've encountered when coming into contact with another persons code.
 
I know a professor here at Clarion that follows all of those.

He calles every function foo or doSomething, it's great for us students who understand but the noobies and the CS minors are totally confused.
 
openParen = (slash + asterix) / equals;

If i have to debug something with this, i swear i'll strangle the programmer!
 
There was a variable named "Fred" in the T1 driver for the product I worked on at my old job.
 
Creative Miss-spelling

If you must use descriptive variable and function names, misspell them. By misspelling in some function and variable names, and spelling it correctly in others (such as SetPintleOpening SetPintalClosing) we effectively negate the use of grep or IDE search techniques. It works amazingly well. Add an international flavor by spelling tory or tori in different theatres/theaters.


Misleading names

Make sure that every method does a little bit more (or less) than its name suggests. As a simple example, a method named isValid(x) should as a side effect convert x to binary and store the result in a database.
 
Definitely a good laugh. What's scarry, some will actually take that write up seriously.
 
Back
Top