Comment Re:My Newbie HOWTO (Score 2) 365
I must take issue with the "programmers don't write good documentation because they are too close to the code". Programmers write lousy documentation for two reasons:
1. They speak English as a second language (okay, this is more applicable perhaps to my current job)
2. They can't write period.
Reason #1 is acceptable to me. I can't speak their language at all, so they're doing me a favor by speaking mine at all. Reason #2 is the overwhelming problem here. Too many people cannot write. Period. This extends far beyond coders; I recently reviewed an essay by an Art student which was almost unreadable, not for all the deconstructionist ArtSpeak, but simply for the poor grammar and spelling.
Okay, now I sound like a bad actor doing a PSA, "stay in school! it's cool!" But hell, take some time when you choose to express yourself, being understood is important.
As for the issue of being able to explain things in a sufficiently coherent manner for newbies: I would challenge you to always strive for this ability. You will find that it forces you to really make sure you understand the ins and outs of whatever technology you work with.
I say this having taught things ranging from ethernet autosensing/negotiation to how to click and drag a file. When you break things down to where you're audience can understand them, you tend to learn a great deal yourself.
1. They speak English as a second language (okay, this is more applicable perhaps to my current job)
2. They can't write period.
Reason #1 is acceptable to me. I can't speak their language at all, so they're doing me a favor by speaking mine at all. Reason #2 is the overwhelming problem here. Too many people cannot write. Period. This extends far beyond coders; I recently reviewed an essay by an Art student which was almost unreadable, not for all the deconstructionist ArtSpeak, but simply for the poor grammar and spelling.
Okay, now I sound like a bad actor doing a PSA, "stay in school! it's cool!" But hell, take some time when you choose to express yourself, being understood is important.
As for the issue of being able to explain things in a sufficiently coherent manner for newbies: I would challenge you to always strive for this ability. You will find that it forces you to really make sure you understand the ins and outs of whatever technology you work with.
I say this having taught things ranging from ethernet autosensing/negotiation to how to click and drag a file. When you break things down to where you're audience can understand them, you tend to learn a great deal yourself.
