Main.ComputingBasics History

Hide minor edits - Show changes to markup

January 26, 2010, at 02:48 PM by 12.13.176.132 -
Deleted line 12:
Changed lines 19-20 from:
  1. Start simple, and expand and modify your codes
to:
  1. Start simple, and expand and modify your codes
  2. Read and learn from good codes
January 20, 2010, at 08:18 PM by 12.13.176.132 -
Deleted line 0:
Changed line 4 from:
  1. Never put blind faith in results generated by software. Always double-check.
to:
  1. Never put blind faith in results generated by software. Always double-check. The best unit for critical thinking is still a human brain.
January 20, 2010, at 08:17 PM by 12.13.176.132 -
Changed lines 1-2 from:

Elements for Computational Work

to:

Elements for Computational Work

Changed lines 11-14 from:

Elements for Good Programming

to:

Elements for Good Programming

January 20, 2010, at 08:17 PM by 12.13.176.132 -
Added lines 1-2:

Elements for Computational Work

Added lines 8-17:

Elements for Good Programming

  1. Think through the project
  2. Use a flow chart to design and organize your ideas and plans
  3. Document your ideas and strategies, explain what you are trying to do
  4. Write clear codes
  5. Start each program with your name, date, version, and purpose of the program
  6. Use informative names for variables
  7. Start simple, and expand and modify your codes
October 28, 2008, at 09:30 AM by 192.203.127.3 -
Changed line 1 from:
  1. As with all experiments, taking notes is the key. Record key procedures and observations so that your work can be reproduced.
to:
  1. As with all experiments, taking notes is the key. Record key parameters, procedures and observations so that your work can be reproduced.
September 10, 2008, at 10:35 PM by 75.143.68.139 -
Changed line 4 from:
  1. Learn to name your files and directories meaningfully and systematically.
to:
  1. Learn to name your files and directories/folders meaningfully and systematically.
September 10, 2008, at 10:34 PM by 75.143.68.139 -
Changed line 3 from:
  1. Make a new directory (or a folder in XP) for each project or task.
to:
  1. Make a new directory (or a folder in Windows) for each project or task.
September 10, 2008, at 10:34 PM by 75.143.68.139 -
Added lines 1-5:
  1. As with all experiments, taking notes is the key. Record key procedures and observations so that your work can be reproduced.
  2. Never put blind faith in results generated by software. Always double-check.
  3. Make a new directory (or a folder in XP) for each project or task.
  4. Learn to name your files and directories meaningfully and systematically.
  5. Backup your data and work directories regularly.