Posts Tagged ‘source code files’

Life of A Programmer — Session 4 — How can you become more skilled than your fellow employees.

August 31, 2013

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

Each of your source code files should not be longer than
three or four pages.

Each source code file should have lots of descriptive
comments.

Each source code file should reference a section of
your plan.

Each variable name should be instantly identifiable.

Keep in mind that your source-code goal is to be able
to instantly relate to its design and use when you open
its file.

You might have to answer a question over the phone a year
after you complete the project.

MORE IN THE NEXT MESSAGE

Advertisements

Life of A Programmer — Session 4 — How can you become more skilled than your fellow employees.

July 10, 2013

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

Each of your source code files should not be longer than three or four pages.

Each source code file should have lots of descriptive comments.

Each source code file should reference a section of your plan.

Each variable name should be instantly identifiable.

Keep in mind that your source-code goal is to be able to instantly relate to its design and use when you open its file.

You might have to answer a question over the phone a year after you complete the project.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4 — How can you become more skilled than your fellow employees.

April 16, 2013

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

Each of your source code files should not be longer than three or four pages.

Each source code file should have lots of descriptive comments.

Each source code file should reference a section of your plan.

Each variable name should be instantly identifiable.

Keep in mind that your source-code goal is to be able to instantly relate to its design and use when you open its file.

You might have to answer a question over the phone a year after you complete the project.

MORE IN THE NEXT MESSAGE

Life of A Programmer — Session 4 — How can you become more skilled than your fellow employees.

February 25, 2013

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

Each of your source code files should not be longer than three or four pages.

Each source code file should have lots of descriptive comments.

Each source code file should reference a section of your plan.

Each variable name should be instantly identifiable.

Keep in mind that your source-code goal is to be able to instantly relate to its design and use when you open its file.

You might have to answer a question over the phone a year after you complete the project.

MORE IN THE NEXT MESSAGE

Can Programming Be Strictly Portable Relative To Language?

February 14, 2013

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

THURSDAY: 2013/02/14 ************************************************

STATUS: The setup software parts which define the comment flag, page size, initial indentation and the indentation increment have been prepared.

NEXT TASK: The software parts which write/certify the output source code files will be prepared next.