Dec. 19th, 2005

livingdeb: (Default)
Today at work I was attacked by one of those annual document readings. I must initial that I have read this document on the proper use of employer-provided technology before they'll let me check my work-related e-mail. There were 26 pages to click through, though they were short pages, more like 13 regular pages.

It turned out to be a pleasant experience. I laughed out loud at this: "If you feel you are being harassed, please report the problem to ... . (Rudeness by itself, however, is not harassment, and neither are other boorish behaviors.)"

Boorish! They used the word boorish in an official document!

Also, you can tell that whoever wrote the document actually has to deal with the issues addressed in the document. I enjoyed the elements of ranting it had. Here's another example:

"Identify yourself clearly and accurately in all electronic communications. Concealing or misrepresenting your name or affiliation to dissociate yourself from responsibility for your actions is never excusable."

And it had very clear descriptions of the topic, based on what is actually done wrong. For example, it mentions things that you might think are okay, but aren't:

"Never use any University-provided computing resource to do something illegal, threatening, or deliberately destructive--not even as a joke. All complaints will be investigated."

Not even as a joke. Just so you know. And additional information on what actually happens:

"If your activity breaks the law, you can be prosecuted. Even if you are not charged criminally, you can still be suspended from the University. Such suspensions happen to several people each semester."

Scary!

Usually these kinds of documents are very general and a bit vague and extremely dry. This one was a bit redundant (though I've seen worse), but very clearly written in a nice easy-to-read style. If you ever find yourself having to write a document like this, I recommend you peruse UT's Acceptable Use Policy for ideas.
livingdeb: (Default)
First, I remembered that although a document has to be saved as text to work in browsers, it needs an .html (or .htm) extension rather than a .txt extension. Duh. Now TextWrangler works fine for me.

Second, I think I've found the book I've been looking for: Beginning JavaScript by Paul Wilton. Amazon reviewers give it 4.5 stars. I found the first edition (2000) in the library, and the 44 pages I've read so far (out of almost 1000) look good. There is a newer edition (2004), but it doesn't look that much better for my needs--the first edition doesn't have some of the outdated things I've been seeing everywhere else, but even the newer edition still has some of them. I may get the next version when it comes out.

Meanwhile, since I'll have to do extra research anyway to make sure I'm following the latest standards, I've decided to use the first edition of this book (which I also just bought online for $1.66 plus shipping). Then I will also use the up-to-date JavaScript Tutorial and try out all my code on various modern browsers.

The book I have been writing is up to 17 pages now, but I don't think I need it. Wilton doesn't explain some of the (few) things I have explained quite as well, but it looks like anything I write would be mostly redundant.

Profile

livingdeb: (Default)
livingdeb

June 2025

S M T W T F S
1234567
891011121314
15161718192021
22232425262728
2930     

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 7th, 2025 12:51 am
Powered by Dreamwidth Studios