Code the component from the design

  • Code the component from the pseudocode and diagrams.
  • Anything tricky, complex, or murky should have been done in the first step or certainly after the design.  If something like this comes up that was overlooked earlier, then stop coding and research it or write a method, class or test program to solve the problem.
  • Follow good coding standards like adding comments that explain what and why something is being done .vs. how.
  • Do not write any unit tests until all of the code for the component has been written.


Prev          Next          Back to efficient software development methodology practices

Copyright 2011 by Robert G. Bryan

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s