Talk:Serial Programming/Introduction and OSI Model

I thank the author of the article for his effort. While admittedly a work in progress, He has set the stage for developing educational activities based on the fundementals of serial communications. I agree that this topic has an ideal basis for curriculum inclusion.

I'm especially thankful of the statement that tags the end with a nice anchor for my own thoughts:
 * ''"This doesn't have to be that complicated of a subject, and it is possible for
 * mere mortals to be able to understand how everything works."

Educational Application
Is this section redundant? Is it really about "intended audience" or should Programming:Serial_Data_Communications be deleted? I recognize that the two sections originally came from different books that are still in the process of merging. --SV Resolution 17:35, 8 September 2005 (UTC)

style guide ; feedback (strictly imo)
If you see how http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00800f9e3a.shtml is written, there is a technical style in use here. I'm not familiar with the rest of the wikibook here to make an absolute judgment. However, it's in my opinion that the style could be changed from a speaker, to a reference. If the goal is to make the content not too technical, I still think it can be accomplished.

Just my two cents. thanks, and good luck. —Preceding unsigned comment added by 66.129.242.4 (discuss • contribs)


 * Keep in mind, this was not intended to be a reference manual originally, but something more of an informal tutorial. I deliberately tried to follow the style used in what IMHO thought was an outstanding tutorial book with Jack Crenshaw's "Let's Build A Compiler!" text (Google the name and you'll find the book).  I certainly didn't want a dry reference manual, as there are dozens of those for serial programming that are available.  In fact, the kind of ultra dry and terse writing that you have given in the above example is precisely what I was trying to avoid.


 * I've sort of run out of steam with this book and haven't really worked on it for... gosh... almost a year now or more. It is something that I want to get back to, and really work on stylistically.  There are a whole bunch of areas that I haven't even touched including some more high-level applications I'd like to get into.  But even so there is some content that can still be useful for understanding the low-level guts of serial communication.


 * I don't want this to sound that I'm "possessive" of this text, and I'm willing to let others "edit mercilessly and redistribute at will". Even so, it is important to know where I was coming from to start this project oh so long ago.  --Rob Horning (talk) 04:11, 29 June 2008 (UTC)
 * Hello Rob. This is a valuable book and the tutorial style is interesting.  Please don't abandon the project.  My first impression is that some of the prose is very wordy and even redundant in places.  Rather than sabotage the tutorial style I suggest making the prose more concise.  I've revised two sentences in the Introduction.  Have a look and revert or revise again according to your preferences.  A good rule in technical writing is to keep sentences short.  That helps a reader focus on a subtle meaning.  Technical prose can also be pleasant to read.  How is that?  Regards, ... PeterEasthope (discuss • contribs) 15:55, 7 February 2018 (UTC)