Busy. Please wait.

show password
Forgot Password?

Don't have an account?  Sign up 

Username is available taken
show password


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.

Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove Ads
Don't know
remaining cards
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
restart all cards

Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

F452 Computing

5 Good Programming Styles

Meaningful identifier names To allow others to understand more easily the purpose and scope of variables. Also applies to names of functions/procedures.
Use of constants For values which do not change e.g. VAT_RATE is easier to understand in an expression rather than 1.2.
Indentation Moving lines of code (to the right) to show clearly where structures start and end. E.g. typically loops/selection.
Modular code Each subroutine does a small part rather than one big program. Easier to identify where something is not working and debug.
Annotate code / Comments Adding comments to code that are not used by the computer so that others can understand the steps of the algorithm.
Use of white space To break code further into logical chunks e.g. separate declarations from statements.
Complex calculations Use extra brackets (parentheses), break up into individual steps in order to make it easier to understand.
Reasons for GPS Teams can work collaboratively. Code can easily be read by other programmers. Program is less error prone.
Created by: Chelsea2760