Linked by Thom Holwerda on Mon 3rd Sep 2012 20:46 UTC, submitted by MOS6510
Thread beginning with comment 533722
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2007-03-26
I think what he/she means is that side effects are bad.
I actually kind of agree with their point. I just think they made their point terribly.
It does make a lot of sense to reuse existing code, not just because it's quicker that writing entire methods from scratch, but because (hopefully) you've already tested that code as well.
Obviously there needs to be a balance though, eg if you're having to kludge together code just to make it possible to paste source from another project, then you really should have been writing that code afresh instead of cutting corners.
But on the whole, programming is as much about reusing existing tools to fix new problems as it is about writing new tools too.
[edit]
--------------------------------------------------
10. Classes should fit on the screen. (+22/-7) by Jay Bazuzi
If you have to use the scroll bar to see all of your class, your class is too big.
Code folding and miniature fonts are cheating.
hahahaha one of my old college lecturers actually used to teach this.
Edited 2012-09-03 22:48 UTC