Welcome to the Lounge

rnbergren wrote:

Another thing I'd like to mention, is that the following {switch} combination: "-O -P Skip" usually doesn't give the results users would expect.

OriginalGriff wrote:

Break the sucker up

I concur with you, with a few caveats:

1. All of the pieces are published within a short period of time.
   
2. The author(s) has had other proofread the entire series, as a whole. The tone, tense, voice, word use, and style should be consistent for the entire series. This is especially important for authors who, like most engineers, did not pay attention during their English Comp. courses. (Many people I've worked with cannot write a decent, error-free one-page memo. English is their primary and, often, only language, yet I shudder to think of them writing a five-to-ten page paper!)
   
3. They include a table of contents (and maybe an index)
   
4. Figures, charts and other inclusions are labeled and numbered.
   
5. The author takes care to define acronyms and unusual technical terms upon first use. We all know what delegates are, what MVVM and FPGA stand for, and how to implement a decision table via linkage editor, right?
   
6. The author(s) cite their source material. If they say they adapted Erin Katzenjammer's technique, please tell us where we can find Katzenjammer's article on the subject. A good hot link is enough. (See The Katzenjammer Kids[^].)
   

Maybe, I am asking for too much.... We are talking about engineers and programmers, after all...

Jalapeno Bob wrote:

Many people I've worked with cannot write a decent, error-free memo.

Jalapeno Bob wrote:

All of the pieces are published within a short period of time.

John Simmons / outlaw programmer wrote:

I edit the article in a HTML file in Visual Studio