1.) elaborate comment, I mean a simple comment like this takes this and puts it in this in this order should be sufficient, if you need pre and post conditions to read a program, you have problems
2.) one time errors, I still have no fucking clue, error } required line blah blah, completly rewrite code, errors still there, exit. come back the next day. compiles fine..... ONGIISNGIKRITGESOIJFOSETIOFJ$%$@TORETJOO!!!!
3.) capitalizing any part of a variable, you know how much more tedious shit that puts on you... herp derp I'lll use string iLikeCocks oops you wrote ilikeCocks compiler error
4.) elaborate variable names that tell you what they're used for - look I can name my variables after pokemon and you should still be able to read it
1. Cryptic software that don't have enough comments. These are often simple comments like this takes this and puts it in this in this order. These are insufficient. I need pre and post conditions to read a program.
2. People who haven't read SICP.
3. Lazy fucks whowritevariablenameslikethis. No capitals whatsoever.
4. Simple variable names that adequately describle what they're used for. For fucks sake people, your identifiers should reflect your interest of the day (like Seaking). It's not supposed to describe your program at all
Name:
Anonymous2010-05-05 23:02
>if you need pre and post conditions to read a program, you have problems
thats called "design by contract" and is considered to be a strong way of proving program correctness as exemplified by the Eiffel programming language
>>1
Maybe if you weren't developing on fucking UNIX in the ancient fucking vi, but rather in a modern operating system which supports IDEs with IntelliSense, this problems wouldn't exist.