If the toilet in the restroom of a favorite restaurant is malfunctioning, do you go and loudly, publicly chew out the assistant cook? You know, rip him or her a whole new one, because of the problem and demand they stop creating new recipes and fix the damned toilet?
Like practically all small to large companies, restaurants require several people, each with different skill sets and job tasks. You wouldn't expect the bus person to cook up your t-bone steak, would you?
"Why are you replacing flowers on that table to make it pretty when my steak isn't done right?!? Damned you!"Naoki has it right - she's dead-on when she says...
"...the introduction of this viewer skin doesn't automatically mean that Linden Lab is collectively huddled around for this Dazzle-movement while shirking more important duties."I mean, bitching at Torley when he posts his weekly tutorials is one thing (shrill off-topic waste of hot air, to be sure - but he is a higher-level Linden... as far as we know) - but to bitch-out Jeremy Linden (knowledge base author) or Pastrami Linden (WindLight developer) about asset server issues or why the hell are teleports not working or login problems is actually nothing more that bitching for the sake of bitching.
I've said it in a previous post.
Not only is it tiring to read these whiny rants, but also each stupid whiny rant takes up one of the precious feedback slots in that blog post. Now, I don't consider myself a Linden Lab fanboi by any stretch of the imagination. I criticize them plenty good. The difference is I am a realist and I do it directly - notecards or emails directly to the appropriate Linden staff.
Naoki also says:
"But they must know by now that this can only make it look as if LL isn't as concerned with fixing what is broken."
Now, transparency also is a double-edged sword. In being transparent as they are, especially with such a blog, anything any Linden says becomes an official statement. Regardless of who that Linden is and what their area of expertise is, and their authorized area of responsibility is.
Hence, I have no doubt each and every Linden who is allowed (yes, allowed) to post on the blog is required to carefully scrutinize what and how anything is said (written) there.
After all, if Jeremy gave any kind of statement whatsoever in answer to questions about the asset server - in his blog post about a tip of the week... it becomes an official statement - at least to any and all who read it. Hence, his authorized, official and appropriate response is "I can't speak to any issues about the asset server, only about the knowledge base".
To every whiner on the blog: well, duh!
So, when Torley posts about "Dazzle" or Jeremy posts about something in the knowledge base - please don't make yourself look like the village public idiot by whining about something else. If you have a critical remark that is on-topic - great! That is what these blog posts are for. To give meaningful feedback.
Now, things have been getting better. WindLight postings for instance. 90% of the replies have been directly about the WindLight viewer. Yes, some of those had to do with the interface, but that's an 'understandable misunderstanding'. It turns out the interface design is being headed up by the team working on the current Release Candidate viewer, which is separate from the WindLight viewer, but the WindLight viewer is based on.
Another thing: if you do post an on-topic 'bitch' about an issue, try to at least explain what is happening, not what is not happening. Simply saying "why does my computer crash every time I try to log on? I'm tired of it!" - doesn't do anything for anyone, especially the Lindens who really want to fix this. oh, and we're all tired of reading it, too.
Rather it would be better to explain in detail - first, try posting the problem in the JIRA - if you don't know how - then ask someone to help you, or even post the problem for you. So a more meaningful blog post might be...
"My system crashes on every login and I suspect it;s the actual viewer, but could be the server - not sure. I've posted the problem to JIRS and here is the link (JIRA LINK)"
- or "...i want to post this problem to the JIRA but I don't know how - can anyone help me? My in world name is First Last"Now this is a good post.
Even better is if you find a problem and have an immediate workaround. What's really bad is when you don't read the original post in full. Like one WindLight release where large black stripes appeared all over the sky. In the original post, it was made absolutely clear that this was happening, that they are aware of and working on it and exactly what to do to eliminate the problem.
Yet, there were a half-dozen posts exclaiming "what is up with the black stripes?!?" "How the hell do I fix this garbage? There's black stripes all over the sky!?!" and so on. Yes, these people don't actually read or try to comprehend the post. Rather, they are in such a hurry to get their whining into this post's feedback that they jump straight to the feedback form to bitch, moan and whine.
So, please...
Read each post and comprehend it it.
Notice who is posting it and think "is this Linden able to have anything to do with any problem I am having - or not?" When you post a feedback - be clear and specific and on-topic. Whether it's kudos or a gripe - if it's on-topic, it's actually helpful to everyone, Lindens included.
Of course, you could always just open your mouth before putting your brain in gear... and remove all doubt.
Do you feel that same way I do? Or are you just one of the hot air dispensers on the LL blog?
1 comments: