This Is For All Us Writers Out There: Oh, and All Us Readers Too!
Do you ever feel like you need a jargon buster just to understand what some companies are saying about their software products?
I know I’ve needed one, and often still do.
I am a content writer and editor for TEC and the learning curve was pretty steep when I started. I mean what is functionality, scalability, dynamic lead
make circuit board
examples, but the examples make it harder to understand. That’s really not the point of examples, now is it? What’s the solution? When writing (white papers, abstracts, case studies, webcasts, podcasts, articles, and so on) about tech concepts and products, DON’T assume your reader is going to understand any of your jargon. If you’ve got to use jargon, explain it. The point is to engage the reader not alienate them.You can lose a reader almost instantly when you start writing like the example