TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
1) The ones that the programmers use tend not to be useful to the
writers or users. Software, like most things, looks different on the
inside than it does on the outside. Programmers care about inside, the
rest of us care about outside. There are a few exceptions. For example,
when I'm programming, I like to know what the compiler is doing to my
code in a fairly detailed way. But those are rare. Programmer flow
charts also tend to be things you don't want your competitors looking
at.
2) Charting is different in object-oriented programming. The classic
flow chart is a tool for procedural languages. Object-oriented code is
usually better charted with entity and relationship charts.
---
mike -dot- huber -at- software -dot- rockwell -dot- com
Home: nax -at- execpc -dot- com
>
