why blog?
well ... for several reasons, really ... i blog cos i like the underlying technology. i think the ppl who wrote the codes did dead brilliant (a trifle redundant, but built-in redundancy is a necessity when working with multiple servers and broad range user ability issues) ...
i blog cos it beats scribbling random thoughts in puter files that clog my machine. no, its not that i write THAT much ... just that file size becomes an issue when ur a nutter like i am about multitasking
and i blog cos i appreciate feedback. writing for the sake of writing and never having anyone read it ... an old prof of mine used to call that literary masturbation LOL! ... blogging isn't the same as reading my work before an audience (what geek EVER wants to do that???) or publishing hard copy ... been there, done both many times, not particularly interested in doing either, ever again. i prefer feedback from ppl who happened to wander in and just had to comment on what they saw.
and lastly? cos it's there. i've been on machines for 30 years now ... i absolutely prefer this over:
- keypunching jcl on cards and praying the registry is on spot;
- dialing (!!) up a remote, waiting for the tone signal and wrestling the handset into the modem cradle;
- whacking out code on a blind terminal only to find out two hours later, that the tech pulled the wrong data tapes;
- explaining to the boss why you HAVE TO backup daily, and how it screwed the inventory when he restored the system with last january's monthly back up;
- writing code for professors who "just want to type the damned thing without memorizing puter schitt" ; or
- dealing with ppl who assume the recycle bin will be emptied by the janitors, delete the programs folder cos "all i do is word," and spray their machines with lysol cos "the computer TOLD me i need antivirus!"
