Research anything that is murky, unclear, or difficult about the programming task first

Before coding, first get all of  your ducks in a row.  So, for example, if there is specialized hardware that the program will be connecting to, then write a class or test program that shows how to utilize that hardware.  If someone else has already done this, then try running that code in debug mode to see how it works.

If there is some sort of programming that looks difficult, complex, or tricky, then solve that problem before tackling the rest of the code.

Solve the hard, tricky parts first before doing anything else.

After all the hard and tricky parts have been solved, then it should be relatively easy to put it all together.


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