Tech writing (multiple response to posts)

Matthew King <[email protected]> wrote:

> Perhaps this is an indication that a vital geek <-> non-geek buffer is
> missing from our dealings with computers, much as a lawyer is a buffer
> between the courts and non-lawyers.

We're already out here. We're those tech writers who do manuals and tech
books that nobody wants to read. ;)

> And if a proto-geek asked for help from a geek, the help received should
> be different from the help received by a developer or a user.

Tech writers call this "knowing your audience."
> 
> To be honest, this is where I feel the business opportunities of Linux
> lie, not selling distributions or providing mere 'support'.

http://www.AnswerSquad.com/ ... feel free to send people our way. ;)

Matthew King <[email protected]> wrote:

> It does come close, doesn't it? It shouldn't though. Ideally the person
> between would be some sort of geek. I like to think I can explain geek
> stuff to users in a fashion they understand. There must be others like
> me.

Again, tech writers. :) We're a whole industry, but somehow a lot of
people either forget or don't know we're there. It's quite lonely. We're
also paid maybe half of what programmers are (if we're lucky), which
explains why there aren't more of us.

-- 
Dee-Ann LeBlanc, RHCE
Lots of things Linux
http://www.Dee-AnnLeBlanc.com/