1.Those who fix code until it compiles.
2.Those who optimize code until it stops compiling.
Name:
Anonymous2009-07-07 4:00
Def #2. I'm not happy until my original 200 lines of messy, patchwork code is condensed into a neat and tidy 50. And then I'll fuss for hours with the formatting until it looks perfect, make sure there aren't any stray tabs or spaces at the end of lines, etc. etc.
DAMN YOU OCD!! >_>
Name:
Anonymous2009-07-07 4:05
3. Those who write code that works the first time and leave it along since they know they've already optimized it the best it can and it compiles.
>>8
Not readability, but efficiency and reliability. The more code there is, the easier it is for shit to fuck up.
Nothing gets my dick harder than finding an obscure command or two that will totally replace some giant subroutine.
Name:
Anonymous2009-07-10 2:43
Nothing gets my dick harder than finding an obscure command or two that will totally replace some giant subroutine.
Name: Email:
12
Entire Thread Last 50 Posts First 100 Posts Thread List Report Thread
DON'T TYPE STUFF HERE
■ ▲ ▼
[4:1] 4chan
1 Name: Anonymous : 2009-07-10 02:13
Name:
FrozenVoid2009-07-10 8:08
>>10 Its something similar to one of Knuth's quotes?
_____________________________________ http://xs135.xs.to/xs135/09042/av922.jpg
Refusal to believe until proof is given is a rational position; denial of all outside of our own limited experience is absurd.