Posts Tagged ‘source 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

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

August 26, 2013

You were recently employed as a software developer in a major software engineering company.

You have a family that needs the financial resources that your job provides.

You need to reduce the risk of layoff and increase the probability of a raise.

Your needs are more likely to be met if you adopt the following four principles.

PRINCIPLE 1: WRITE AND EXECUTE A PLAN

PRINCIPLE 2: KEEP A WRITTEN DAILY LOG

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

MORE IN THE NEXT MESSAGE

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.

July 7, 2013

You were recently employed as a software developer in a major software engineering company.

You have a family that needs the financial resources that your job provides.

You need to reduce the risk of layoff and increase the probability of a raise.

Your needs are more likely to be met if you adopt the following four principles.

PRINCIPLE 1: WRITE AND EXECUTE A PLAN

PRINCIPLE 2: KEEP A WRITTEN DAILY LOG

PRINCIPLE 3: MAKE SMALL SELF-DOCUMENTING SOURCE FILES.

PRINCIPLE 4: ACCEPT NO VERBAL ORDERS

MORE IN THE NEXT MESSAGE

Open Source Software Development Tool: Upgrade Progress

May 17, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY: 2013/05/17

STATUS: The modifications to the precoper source file needed to
implement the _SEGMENT_READ and _SEGMENT_WRITE” continue. The utility
subroutine “segment_in”, the basic routine for _SEGMENT_READ, has been
prepared and compiled.

DETAIL: At the present time, the state machine needed to insure
operation has not as yet been prepared.

NEXT TASK: The next task is to implement the commands, _READ_SEGMENT,
commands in the precoper source files and associated header files.

Open Source Software Development Tool: Upgrade Progress

May 3, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY: 2013/05/03

STATUS: I examined the precfile source code relative to a write_segment
instruction and have found it to be adequate.

NEXT TASK: The next task is to add a the new commands, _READ_SEGMENT
and _WRITE_SEGMENT commands to the precoper source files and associated
header files.

Open Source Software Development Tool: Upgrade Progress

April 27, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY: 2013/04/27

STATUS: I examined the segmented read and conventional read text
process and have found that both processes are fully functional
independently of whether the segment read has finished reading a line
before a conventional read line command is issued.

DETAIL: The problems will occur in the management of the commands.
Specifically, problems may result if a _READ_TEXT command is issued
before the end of the line is discovered by the _READ_SEGMENT command.
Management of the commands will be accomplished in “precoper” routines,
not the “precfile” routines.

NEXT TASK: The next task is to modify the “precfile” source files to
accommodate a new write segment instruction.

Open Source Software Development Tool: Upgrade Progress

April 19, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

FRIDAY: 2013/04/19

STATUS: The restoration of the Programmable Software Development
Environment has been completed.

DETAIL: The srcproj source file and the associated header files have
been modified and tested.

NEXT TASK: The next task is to modify the precfile source files to
accommodate the new read segment instruction.

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