Linked by Thom Holwerda on Mon 24th Sep 2012 15:07 UTC, submitted by MOS6510
Thread beginning with comment 536304
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2007-09-23
Interesting way to look at it.

I guess I would fall somewhere between engineer and computer scientist. I love to build reusable, well structured and documented projects which preferably solve interesting problems with elegant algorithms.
I really do agree that many computer scientists write very messy code. Especially the ones coming from the fields of mathematics where they are used to naming variables a, b, c... and x, y, z... Most of us coming from the "other end" (self learned, developer way) are not very used to reading stuff like that.
I prefer descriptive names for my variables in code. The one-letter names are reserved for pure mathematics during modeling.