Programming.ProgrammingTechnique History

Hide minor edits - Show changes to output - Cancel

 
 
February 26, 2009, at 08:50 AM by OtherMichael -
Changed line 15 from:
Attach:IT/TheFineArtOfCodeCommenting.pdf
to:
Attach:TheFineArtOfCodeCommenting.pdf
Changed line 25 from:
*[[http://www.devx.com/java/Article/9305|Two Critical Tips for Unit Testing in Jav]]
to:
*[[http://www.devx.com/java/Article/9305|Two Critical Tips for Unit Testing in Java]]
 
 
November 26, 2008, at 09:29 AM by OtherMichael -
Changed lines 7-10 from:
*[[http://www.joelonsoftware.com/articles/Wrong.html|Making wrong code look wrong]]
*JaVa.CodingConvention

to:
[[http://www.joelonsoftware.com/articles/Wrong.html|Making wrong code look wrong]]

Added line 12:
Stack Overflow: [[http://stackoverflow.com/questions/304876/annoying-or-idiotic-naming-conventions|naming conventions]]
 
 
September 22, 2008, at 04:23 PM by OtherMichael -
Deleted line 2:
use the [[IT.TortoiseCVS|CVS]]
Changed lines 9-12 from:
*VisualBasic.CodingConvention
*InputAccel.CodingConventions
*FormWare.CodingConventions

to:

Changed lines 35-37 from:
*per EMC/Captiva support (cc Nov 2006), there are no existing Unit Testing frameworks that work with the FormWare VBA. They would be happy to have us pay them to develop one, however. Side note: don't see how it would be possible to integrate into InputAccel.

to:
Deleted line 40:
IT.ProgrammingLanguages
Changed line 44 from:
[[!Programming]] [[!Design]] [[!BestPractices]]
to:
[[!Programming]] [[!Design]] [[!BestPractices]]
 
 
June 06, 2008, at 09:11 AM by MichaelPaulukonis -
Added lines 13-14:

Code is read more often than it is written. It need to be both machine-readable, and human-readable. If your coworkers cannot read and make sense of your code quickly, it is poorly written.
 
 
March 12, 2008, at 02:55 PM by MichaelPaulukonis -
Added line 20:
http://particletree.com/features/successful-strategies-for-commenting-code/