<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0"><id>tag:blogger.com,1999:blog-13873728</id><updated>2008-04-01T04:38:14.502-05:00</updated><title type="text">technically speaking</title><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default?start-index=26&amp;max-results=25" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>64</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/blogspot/techspeak" type="application/atom+xml" /><feedburner:browserFriendly></feedburner:browserFriendly><entry><id>tag:blogger.com,1999:blog-13873728.post-2911343886298223133</id><published>2008-04-01T04:34:00.002-05:00</published><updated>2008-04-01T04:38:14.583-05:00</updated><title type="text">What We Do</title><summary type="text">One of the tech writers here at NI Shanghai has posted a great entry describing what she does all day. Now, we don't do all of this stuff every day. But a large majority of it will be done over the course of a week or so. At any rate, it's a great peek into just what life is like at the office -- because I know you all were curious about exactly that :-)
</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2008/04/what-we-do.html" title="What We Do" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=2911343886298223133" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/2911343886298223133/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/2911343886298223133" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/2911343886298223133" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-2936120034721057890</id><published>2008-03-21T03:46:00.002-05:00</published><updated>2008-03-21T04:14:18.558-05:00</updated><title type="text">No English Spoken Here</title><summary type="text">I've never had the opportunity to learn a foreign language before, outside of the pidgin-Spanish I can remember from 7th-8th grade. Coming to Shanghai and attempting to learn Mandarin has been an adventure. A frustrating and difficult adventure, but a worthwhile and rewarding one also.

At the same time as I'm trying to learn a new language (or at least get some basic handle on it), I'm reviewing</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2008/03/no-english-spoken-here.html" title="No English Spoken Here" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=2936120034721057890" title="1 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/2936120034721057890/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/2936120034721057890" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/2936120034721057890" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-2497355930963935352</id><published>2008-03-04T03:58:00.002-06:00</published><updated>2008-03-04T04:05:21.894-06:00</updated><title type="text">Non-trivial Typos</title><summary type="text">From now on, I'm going to start filing typos as bug reports that are far more serious than "trivial".
Barry Bonds seized on a pair of typos, complaining in court papers Thursday that the government's mistakes could compromise his chances for a fair trial. The typographical errors showed up in a recent filing by prosecutors wrongly accusing Bonds of flunking a drug test in 2001. They later </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2008/03/non-trivial-typos.html" title="Non-trivial Typos" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=2497355930963935352" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/2497355930963935352/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/2497355930963935352" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/2497355930963935352" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-7339836379134876893</id><published>2008-02-10T21:27:00.000-06:00</published><updated>2008-02-10T21:56:38.926-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="reader" /><category scheme="http://www.blogger.com/atom/ns#" term="reviewing" /><category scheme="http://www.blogger.com/atom/ns#" term="adobe" /><category scheme="http://www.blogger.com/atom/ns#" term="digital" /><title type="text">Digital Reviewing</title><summary type="text">For the 3+ years I've been at NI, I have been reviewing documents by printing out hard copies and distributing them to reviewers. However, now that I am doing more reviewing than writing, I've fallen in love with the commenting features of Adobe Reader. The process works like this:
Create CHM or PDF files.
Print CHM file to a PDF file. We can do this because we have Acrobat installed.Enable PDF </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2008/02/digital-reviewing.html" title="Digital Reviewing" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=7339836379134876893" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/7339836379134876893/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/7339836379134876893" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/7339836379134876893" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-3750916945016928689</id><published>2007-12-27T12:57:00.001-06:00</published><updated>2007-12-27T13:55:13.593-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="documentation development" /><category scheme="http://www.blogger.com/atom/ns#" term="international" /><title type="text">From a Distance</title><summary type="text">(Side note: Every time I see the acronym for Subject Matter Expert, I think of Smee from Captain Hook.  Every time.)

Through a co-worker's blog, I came across a post about sitting near your SME at the office.  I cannot agree more emphatically.  At NI, most of technical writers sit in the same general location as the engineers for whom they write documentation.  For most of my three years here, I</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/12/from-distance.html" title="From a Distance" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=3750916945016928689" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/3750916945016928689/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/3750916945016928689" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/3750916945016928689" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-1739028366303771237</id><published>2007-11-27T10:09:00.000-06:00</published><updated>2007-11-27T11:25:44.298-06:00</updated><title type="text">It's Been Awhile ...</title><summary type="text">...but I wanted to link to two posts I saw on the User Advocacy blog:Technical Writing in Transition: Part 1 and Part 2.Makes for some interesting reading, I think.Quote:
Technical writing has adapted with three fundamental changes:

1. Task-oriented writing. Instead of describing the parts of a system, we walk the user through tasks and explain technical knowledge incidentally.
2. </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/11/its-been-awhile.html" title="It's Been Awhile ..." /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=1739028366303771237" title="1 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/1739028366303771237/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/1739028366303771237" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/1739028366303771237" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-4201898290843355260</id><published>2007-08-03T15:24:00.000-05:00</published><updated>2007-08-03T15:33:52.690-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Coolest Things I've Ever Seen" /><title type="text">Beatboxing with LV FPGA and PXI</title><summary type="text">File this one under "Coolest Things I've Ever Seen."  Vineet samples himself beatboxing and singing.  He can do this multiple times until he is giving himself a full backing melody.

His mic is hooked into a PXI-7831R running LabVIEW FPGA.  The performance is from the NI Live Talent Show we have once a year; this one was on July 12 2007.

Watch this one to see Vineet turn it up a notch!

Try </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/08/beatboxing-with-lv-fpga-and-pxi.html" title="Beatboxing with LV FPGA and PXI" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=4201898290843355260" title="1 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/4201898290843355260/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/4201898290843355260" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/4201898290843355260" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-2369520346965235688</id><published>2007-08-02T15:30:00.001-05:00</published><updated>2007-08-02T15:33:34.627-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="NIWeek" /><title type="text">NIWeek 2007</title><summary type="text">NIWeek 2007 starts next Tuesday, August 7th at the Austin Convention Center!  This year, instead of simply attending, I'm giving a presentation!  Here's the info:

Date / Time: Wednesday August 8th, 3:30 PM.  Room 16A.
Title: Documentation Dividends: Help that Pays Off
Abstract: Well-planned product documentation can save time, reduce customer frustration, and improve your product’s reputation. </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/08/niweek-2007.html" title="NIWeek 2007" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=2369520346965235688" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/2369520346965235688/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/2369520346965235688" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/2369520346965235688" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-8630752688799592874</id><published>2007-06-28T08:44:00.000-05:00</published><updated>2007-06-28T09:36:50.722-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="perforce" /><category scheme="http://www.blogger.com/atom/ns#" term="documentation development" /><category scheme="http://www.blogger.com/atom/ns#" term="lone writer" /><category scheme="http://www.blogger.com/atom/ns#" term="source code control" /><title type="text">Source Code Control for Documentation</title><summary type="text">Jim Kring and Joel Sumner have posted recently about the benefits of source code control (SCC) for software development.  At NI, the technical writers also use SCC for our documentation development. For those who are unfamiliar with SCC, it works like this:
Your source files are stored in a repository on a central server.To edit a source file, you must "check out" the file.  Checking out a file </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/06/source-code-control-for-documentation.html" title="Source Code Control for Documentation" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=8630752688799592874" title="1 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/8630752688799592874/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/8630752688799592874" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/8630752688799592874" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-8111819621420260240</id><published>2007-06-18T17:31:00.000-05:00</published><updated>2007-06-18T17:32:57.311-05:00</updated><title type="text">Documentation is Important</title><summary type="text">Even our developers think so :-)
</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/06/documentation-is-important.html" title="Documentation is Important" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=8111819621420260240" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/8111819621420260240/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/8111819621420260240" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/8111819621420260240" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-2229592777274399893</id><published>2007-06-08T14:52:00.000-05:00</published><updated>2007-06-08T14:54:20.284-05:00</updated><title type="text">What We Do All Day, Part 2</title><summary type="text">Interested in working as a technical writer but don't know what it is that we do?  Our Texas Tech recruiting team gathered some alumni and put together an informative video that consists of interviews with technical writers and managers here at NI.  The video also has some great tips for those who are applying for technical writing jobs.  Top tip: Proofread your resume! :-)</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/06/what-we-do-all-day-part-2.html" title="What We Do All Day, Part 2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=2229592777274399893" title="3 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/2229592777274399893/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/2229592777274399893" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/2229592777274399893" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-4830361157487735425</id><published>2007-05-25T09:16:00.001-05:00</published><updated>2007-05-25T10:08:26.026-05:00</updated><title type="text">Split over Splits</title><summary type="text">At NI we have a company-wide style guide.  One of the weirdest things about it, and something which I've had the most trouble getting used to, is the guideline against splitting verbs.

Before I came to NI, I'd write a sentence like this:

You can also double-click the Add function.

But now I write like this:

You also can double-click the Add function.

Also:

You must manually specify the </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/05/split-over-splits.html" title="Split over Splits" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=4830361157487735425" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/4830361157487735425/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/4830361157487735425" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/4830361157487735425" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-7280403227240378144</id><published>2007-05-16T09:41:00.000-05:00</published><updated>2007-05-16T09:49:57.405-05:00</updated><title type="text">The LabVIEW Documentation that Anyone Can Edit</title><summary type="text">I don't know how I missed this, and I apologize for not posting it sooner!  For those of you who are familiar with wikis, the LAVA (LabVIEW Advanced Virtual Architects) group has a wiki for LabVIEW.  I encourage you all to go and contribute your knowledge to this compendium.  Communication among customers about LabVIEW always is a good thing.  It will be interesting to see how this wiki compares </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/05/labview-documentation-that-anyone-can.html" title="The LabVIEW Documentation that Anyone Can Edit" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=7280403227240378144" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/7280403227240378144/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/7280403227240378144" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/7280403227240378144" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-396863719855301008</id><published>2007-05-11T11:13:00.000-05:00</published><updated>2007-05-11T14:47:19.614-05:00</updated><title type="text">Improving the Readability of Text Online</title><summary type="text">A company called Walker Reading Technologies has produced research showing that the human brain is not "wired" to read text in the traditional way we print it, which is in blocks.  In short, we're constantly filtering out text that surrounds what we're trying to actually read.  This filtering impedes our comprehension of the material.

Supposedly, the optimal format is a series of "short, </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/05/improving-readability-of-text-online.html" title="Improving the Readability of Text Online" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=396863719855301008" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/396863719855301008/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/396863719855301008" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/396863719855301008" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-491699614114804293</id><published>2007-01-11T13:06:00.000-06:00</published><updated>2007-01-11T13:39:53.041-06:00</updated><title type="text">A Guide to LabVIEW Documentation, Part 1</title><summary type="text">As part of a great effort between our technical writers and the SW developers, LabVIEW has multiple entries into the LabVIEW Help.  The LabVIEW Help itself is huge, which is mostly a function (hah!) of the number of things you can do with LabVIEW.  Additionally, because many LabVIEW customers use the product to make other products, we have to account for a lot of use cases, generalities, and </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/01/guide-to-labview-documentation-part-1.html" title="A Guide to LabVIEW Documentation, Part 1" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=491699614114804293" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/491699614114804293/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/491699614114804293" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/491699614114804293" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-7672638099349744489</id><published>2007-01-08T10:05:00.000-06:00</published><updated>2007-01-08T10:34:33.899-06:00</updated><title type="text">Horn Tooting</title><summary type="text">I opened my inbox this morning and found an email from my dad.  He  congratulated me because NI made FORTUNE magazine's "Top 100 Companies to Work For" list for the 8th consecutive year.  I seem to remember that last year we were higher in the rankings, but being in the list is a good thing all by itself.  It would have been neat to have been able to participate in the employee survey, but it's </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2007/01/horn-tooting.html" title="Horn Tooting" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=7672638099349744489" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/7672638099349744489/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/7672638099349744489" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/7672638099349744489" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116406885528078047</id><published>2006-11-20T18:12:00.000-06:00</published><updated>2006-11-20T18:36:07.586-06:00</updated><title type="text">NI-TC 2006</title><summary type="text">Every year at NI, we have an internal conference for all the employees in the Technical Communications department. This conference, conveniently enough called NI-TC (for NI-Tech Comm) is in late October and lasts for two days. It's a time for us to bring everyone up to speed on what's going on the department. We have multiple presentations/seminars, a demo fair that showcases the neat products we</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/11/ni-tc-2006.html" title="NI-TC 2006" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116406885528078047" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116406885528078047/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116406885528078047" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116406885528078047" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116291529939857625</id><published>2006-11-07T09:48:00.000-06:00</published><updated>2006-11-07T10:02:23.540-06:00</updated><title type="text">What We Do All Day</title><summary type="text">6-7 years ago, NI created a website, in partnership with Texas Tech University, that walks you through A Week in the Life of a Technical Communicator.  Because the design is so 90s, and because the "star" of the web site is no longer with NI, in January 2006 a group of writers decided to update the site with a more "modern" look.  (Wow, that's a lot of quotes here.)

The result is a </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/11/what-we-do-all-day.html" title="What We Do All Day" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116291529939857625" title="4 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116291529939857625/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116291529939857625" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116291529939857625" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116284630079599050</id><published>2006-11-06T14:46:00.000-06:00</published><updated>2006-11-06T14:52:58.943-06:00</updated><title type="text">Guest Appearance on the VI Road Show</title><summary type="text">Every Halloween, the LabVIEW team sets up various demos of our products for other members of the company.  This year, the VI Road Show invaded and caught some of what went on.  The following video shows Varun, myself, and Alex discussing and demonstrating the LabVIEW Simulation Module.  Beware the horrible scrolling CRT monitors!
 
P.S:  I feel I should explain my bloody face :-)  My costume this</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/11/guest-appearance-on-vi-road-show.html" title="Guest Appearance on the VI Road Show" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116284630079599050" title="3 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116284630079599050/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116284630079599050" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116284630079599050" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116198538684809419</id><published>2006-10-27T16:32:00.000-05:00</published><updated>2006-10-27T16:44:00.996-05:00</updated><title type="text">Not an Engineer</title><summary type="text">I was re-reading the post about April's interview in the Statesman, and the last sentence stuck out at me:
...the fact that she is not a programmer or engineer serves her well as a tech writer.
This phrase is very true.  I said the very same thing to a class of students at UTSA last fall, and I find myself thinking it at the career fairs I've been to recently.  Many job applicants hear "technical</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/10/not-engineer.html" title="Not an Engineer" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116198538684809419" title="3 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116198538684809419/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116198538684809419" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116198538684809419" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116136663764137518</id><published>2006-10-20T12:49:00.001-05:00</published><updated>2006-10-20T12:50:37.663-05:00</updated><title type="text">The VI Road Show</title><summary type="text">Welcome the newest NI Blog member - the VI Road Show.  This is actually a vlog (video blog) that will take you around the country (and possibly world) as the owners showcase NI's employees and customers.
</summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/10/vi-road-show_20.html" title="The VI Road Show" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116136663764137518" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116136663764137518/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116136663764137518" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116136663764137518" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116120987335771628</id><published>2006-10-18T17:14:00.000-05:00</published><updated>2006-10-18T17:20:34.266-05:00</updated><title type="text">Interview w/April Brinkmeyer</title><summary type="text">The Austin American-Statesman recently interviewed a co-worker of mine, April Brinkmeyer.  She is a technical writer for the LabVIEW core product.  Here's a snippet:

Writing, reviewing, updating and improving the program's extensive help documentation in-program, in print and online is an on-going project for Brinkmeyer and the others on the documentation team. She also sits on committees that </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/10/interview-wapril-brinkmeyer.html" title="Interview w/April Brinkmeyer" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116120987335771628" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116120987335771628/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116120987335771628" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116120987335771628" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-116049628624107629</id><published>2006-10-10T10:52:00.000-05:00</published><updated>2006-10-10T11:20:51.646-05:00</updated><title type="text">UI, Documentation, and Polish</title><summary type="text">I'm not sure how it is at other places, but part of being a technical writer at NI is dealing with usability.  We are often the first non-engineers/non-developers to see a feature in action.  We come across many malformed and confusing dialog boxes, interface widgets, organizational structures, and so on.   In LabVIEW we have a great usability advocate in  Christina Rogers, who recently made a </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/10/ui-documentation-and-polish.html" title="UI, Documentation, and Polish" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=116049628624107629" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/116049628624107629/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/116049628624107629" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/116049628624107629" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-115989299903315359</id><published>2006-10-03T11:25:00.000-05:00</published><updated>2006-10-03T11:29:59.046-05:00</updated><title type="text">Bloggers vs. High Schoolers in Writing Competition</title><summary type="text">/. has a bit this morning about bloggers competing with high schoolers on the SAT essay.  If you like, you can even rate the bloggers' submissions yourself!

Here's the essay question, timed at 20 minutes:
Directions: Think carefully about the issue presented in the following excerpt and the assignment below.

I have learned that success is to be measured not so much by the position that one has </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/10/bloggers-vs-high-schoolers-in-writing.html" title="Bloggers vs. High Schoolers in Writing Competition" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=115989299903315359" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/115989299903315359/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/115989299903315359" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/115989299903315359" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-13873728.post-115877676623287111</id><published>2006-09-20T13:22:00.000-05:00</published><updated>2006-09-20T13:35:44.613-05:00</updated><title type="text">Interviewing</title><summary type="text">Since the day I started at NI, I knew I wanted to be involved in recruiting technical writers.  We have a dedicated HR department at NI, but the people you see at career fairs are regular full-time employees.  I like this method much better than having recruiters represent us, because I know more about technical writing at NI than the HR people do.  Therefore, when students come up to me or I </summary><link rel="alternate" type="text/html" href="http://lvtechspeak.blogspot.com/2006/09/interviewing.html" title="Interviewing" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=13873728&amp;postID=115877676623287111" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/115877676623287111/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://lvtechspeak.blogspot.com/feeds/posts/default/115877676623287111" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/13873728/posts/default/115877676623287111" /><author><name>Ryan</name><uri>http://www.blogger.com/profile/13544462798718591052</uri><email>noreply@blogger.com</email></author></entry></feed>
