Skip to main content
CS Teaching Tips

Main navigation

  • Browse All Tips
  • Tags
  • 3D
  • About
  • Rate Tips
  • Tip Sheets

Remind students that it’s better for time management and project outcomes to get code reviewed after each small change is made.

Share Remind students that it’s better for time management and project outcomes to get code reviewed after each small change is made. with FacebookShare Remind students that it’s better for time management and project outcomes to get code reviewed after each small change is made. with Twitter
  • If students make a lot of changes before testing, it is harder to keep track of what was changed. This can make debugging more time consuming and difficult, because they will often not know where their program is wrong or why their code isn't working.

More about this tip

Tags

  • Development Methods
External Source

"So you want a code review... " by Ellen Spertus, under "Keep it simple"

Other Tips By
Other Tips By Ellen Spertus

Similar tips

Use the playful phrasing “bracket thief” when students get a common Java error for forgetting to use a closing bracket to remind students of this error in a non-threatening way.
Have students play the Gidget debugging game for practice debugging in an engaging environment.
Have students compete calculating to the 50th Fibonacci number, one team of humans doing the math versus a team students writing a program to stress the importance of computing for calculations.

For more information or to report a bug, contact us at admin@csteachingtips.org. Built with Bootstrap. Powered by Drupal.

Privacy Policy