1. Technical Communications and Programming: The Economic Reasons for Commenting
(Technical Communication/Technical Communication Lessons)

... on maintaining their own software (1; 2; 3). Labor, specifically the amount of time spent by maintenance programmers understanding another person’s code, obviously accounts for a large portion of the cost. ...

2. Technical Communication and Programming: Dissertation Study
(Technical Communication/Technical Communication Lessons)

Okay, recently I've had a lot of interest in my research into source-code comments. A bulk of my research was carried out during my doctoral dissertation study: a four-month long case study in which I ...

3. Technical Communication and Programming: Internal and External Documentation
(Technical Communication/Technical Communication Lessons)

... code, while external documents are needed to give context to the program itself. Internal documentation serves a basic function: it helps people more quickly and easily understand the code. This is accomplished ...

4. The Use of Programming Source-Code Comments
(Technical Communication/Technical Communication Lessons)

Attached to this is a rather long article drawn from my dissertation research on the use of source-code comments in programming. Why is it published here rather than elsewhere? Well, the simple answer ...

5. When To Use Graphics
(Technical Communication/Technical Communication Lessons)

... cues help us quickly find information. This is true of things like labels within images, but also true for other visual cues: such as page numbers or color coded elements. Things like section headings, ...

6. Technical Communication and Programming: Using Writing Rules
(Technical Communication/Technical Communication Lessons)

... write better documents is, after all, my occupation; and believe it or not the principles I teach to write better papers are not that different from the principles needed to write better code. Of course ...

7. Name
(Contact / Contacts)

Name, Position, Miscellanous info