![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Writing documentation is just programming.
You're programming a human being to operate your software.
Too bad the programming language is complex, ad hoc, crufty, poorly
defined and virtually impossible to debug...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> Writing documentation is just programming.
>
> You're programming a human being to operate your software.
>
> Too bad the programming language is complex, ad hoc, crufty, poorly
> defined and virtually impossible to debug...
Another problem is that it's hard to write unit tests. But I keep thinking I
should write a tool for that, using extra metadata. At least for basic
things like remembering to remove documentation for removed features.
Click the 'Attach file' button on the toolbar.
<% assert(toolbar.actions.contains("Attach file")) %>
If the button is removed or renamed, the failing test would remind me to
update the documentation.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> Writing documentation is just programming.
>
> You're programming a human being to operate your software.
>
> Too bad the programming language is complex, ad hoc, crufty, poorly
> defined and virtually impossible to debug...
And there are often bugs in the hardware.
Regards,
John
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> Too bad the programming language is complex, ad hoc, crufty, poorly
>> defined and virtually impossible to debug...
>
> And there are often bugs in the hardware.
Perhaps you mean wetware? ;-)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |