yesthattom (
yesthattom) wrote2007-01-08 01:56 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Fortune published "100 Best Companies to Work For"
Google is #1. This is the first year they qualify to be on the list, so starting out at #1 is pretty cool.
In a related note, I really do like working here. ...and I’m hiring... ...in NY, Zurich, and Mountain View...
In a related note, I really do like working here. ...and I’m hiring... ...in NY, Zurich, and Mountain View...
no subject
no subject
no subject
I'm competent to publish in English and Esperanto. I can get by in French and Dutch, and have some understanding of Russian and Yiddish.
no subject
no subject
no subject
Please do not assume that I don't know what I am talking about or have not done research, simply because I opine that he might prefer to write for a public publisher instead of a private company.
no subject
no subject
Hopefully my reply to him below clarified the reason for my opinion.
I am still not quite sure why you friended me, but have no particular desire to start communications on a hostile note. So no offense taken, hopefully none given. I can be a snarky wiseass sometimes, but I'm not here to piss anyone off.
no subject
no subject
But maybe I should revisit O'Reilly... after all, Tom's book isn't really about *technology* per se...
no subject
My own opinion is that a lot of the people who write for O'Reilly are considered industry leaders not only because they understand the technology in detail, but because they also know how to explain it in an accessible manner to people who've never seen it before.
Private company technical writing can vary wildly in comparison. You can get a lot of excruciating technical specifics that need to stay company internal, or they'll striate versions of the data based on support contract level (or in the military, security classification). The lifespan of a document can be very short. Of course, that's job security right there, but it seems to me that a product and it's documentation should be robust enough to last for a while. Once you're on the inside you're documenting bugs, patches, version upgrades and spec changes galore. I worked at Sun for four years, and geez o pete but those people went through the dead trees (or digital equivalent) when it came to documentation.
I guess it's all about what you want to write. I can't see myself as a technical writer, dude, especially the company internal kind, so more power to ya. I'd probably get pissed off at having to constantly twiddle a document to fit a product, to the point where I'd just want to fix the product to fit the document instead. :D
Nice that you covered the Asia Society. I was there recently. They've added an audio presentation that you can access via cel phone as you walk around the exhibits.
no subject
no subject
no subject
I'm going to turn my answer into a full post next week.
no subject
People should steal it, and threaten to beat you up if you ask for it back.
You should buy dozens of copies and hand them out rather than risk daggers and funny looks when you ask for it back.
(Wow, I gotta cut down on the caffeine and askaninja.com videos)
no subject
no subject
The tabletop article was fun to do.
no subject