What kind of content keeps you reading?

[bcwilson]

At NI, we're very interested in learning about how our customers use our products and then sharing that information with the engineering community.

We share this content in a variety of ways, including case studies, blog posts, and various newsletters. So we want to know what works for you.

If you're getting ready to purchase a new product or looking for some inspiration on solving a problem, what kind of content do you find valuable? Do you like reading case studies on how other people solve their problems? Or maybe you always turn to the forums or white papers?

Let us know what kind of content catches your eye and why it keeps you reading!

Brittany Wilson

NI Content Specialist

[hpman]

Info about new product and what is improoved. Interested in aplication notes, how other people resolved problems.

Price info is also important.

I am not sure if you also give service notes (known problems, hardware and software,) and how to resolve them.

I wish you success in bussiness, Boris Hrib

[Ben]

Hi Brittany,

I suggest you study very closely all of the posts by Greg McKaskle. It was his posts that got me hooked in the first place.

Greg was very active in the forum prior to LV 7.0. At that time he was locked up in the ivory tower and we have seen scarse little form him. But when we do we get posts like the "Clear as Mud" thread.

If you want more readers and to keep them;

1) Let Greg out of his cage and tell him it is OK for him to answer questions.

2) Encourage others from R&D that there is nothing wrong or dirty about answering questions in the forums.

3) Bring back DR. VI.

4) Include a minimum number of posts on the forums by R&D in their job requirements so they have to answer if they want a raise.

Just my 2 cents,

Ben

[Joel_in_Calif]

I enjoy reading the practical LabView examples on implementing different DAQ features.  I read all the NI-DAQ Examples postings and those submitted by college students.

[Process_Systems]

Just about the current mix of subjects is a nice ballance. I particularly like the tech tips and tricks, but I don't skip over any ot the subject matter.

[Wayne.C]

Good Morning Brittany,

What keeps me reading is 'real' content that has technical depth.  Robot 'Johnny 5' in the movie Short Circuit said it best, "Need input!".  The actual format it is presented in really doesn't matter. 

I agree with Ben that R&D should be encouraged/allowed to venture out on occasion.

[maxarmor]

I enjoy the Newsletters.

I like to see what it takes to inspire people to learn more and then how they solve their problems. I like creativity in general.

I like to know when companies and other groups find ways to help people that need help. I include the person with the great ideas that can't afford the professional tools in the group of people that need help. I wish more companies would cater to the independent hobbyists and experimenters.

I also like the interactions at users groups. How do you get that live interaction into print?

[bcwilson]

Hi, thanks everyone, I really appreciate you taking time to provide feedback. It definitely gives the content team some things to think about... ways to unleash R&D and 'how to get that live interaction into print.' Perhaps some 'Ask the Engineer' columns are in order.

Be sure to subscribe to our newsletters if you're interested. We are always looking to the forums for content ideas, whether in a straighforward way like this, or just seeing what constitutes a hot topic, so thanks again!

Brittany  

[Ben]

Please tell Greg that we miss him and he is always welcome to come back and visit us.

Ben

[Ray.R]

I'm a just getting involved with Wireless Sensor Nodes (WSN) and the new (not yet released) WSN-3214.

So I read the Tutorials and whatever information I could find.  Then I talk to the Application Engineers.

It would be good to publish even the draft user manuals so that we can be informed when making decisions.

Knowledge Base is also good.

At such an early stage, it is difficult to ask questions on the forum, because... well...  development has not yet started and I'm not "stuck".. so asking questions about a product that is not "out there yet" would be futile..  Hence having access to draft documents would be helpful.