I can see your point.

I may try to pull some of the stuff I have in my FAQ's and post it to the Wiki. At least that way it could be added to over time and edited by folks who are smarter than me.

Pete


Scott Klement wrote:
Actually, I've tried several times to write articles about this stuff... but it's hard to really nail down what I need to cover, and what I don't, and what order to cover it in.

It's a lot easier to explain in a situation like this where you have a particular application in mind, and I just have to tell you how to do it. But writing something general that explains everything is a lot harder... I've been working in this type of environment so long that (until someone asks) it's hard for me to see what people will understand and what they won't.

Another consideration is that I typically write articles that are meant to be short enough that you can read them on a coffee break (or at least a lunch hour) as opposed to full-sized books. And I wonder if there's too much here for a short article...


Pete Helgren wrote:
First, thanks for your patience and, if you are ever wondering about writing an article and needing an idea, an article about the all the AIX environment lingo and what they mean would be great. Differentiating between programs run through Qshell and QP2Term. Understanding what the different AIX and AIX-like environments can do, what they support and how to access them would be great. I have tried to build an FAQ from posts here in Midrange, but, as you no doubt have noticed, I still have a lot of learning to do. (Perhaps you already have such an article and I just missed it...)


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].