Azure Jane Lunatic (Azz) 🌺 (
azurelunatic) wrote2006-12-15 02:29 am
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Entry tags:
I trust the LJ development team. Do you?
I trust LiveJournal's development team to have LiveJournal's best interests at heart, to lead LiveJournal in a good direction, and to listen to constructive feedback.
I will do my best to make the feedback I leave for LiveJournal developers constructive in nature.
If you wouldn't do it in fandom, don't do it to the devs. I know that this is the choir section here that I'm ranting at, but I've spent the past couple hours in a room with some rather irritated engineers who are really code people, not people-people. They've been busting their asses for months to track down random crap that goes wrong. This site is so bloody huge and robust that Bantown could not take it down for long, even though they tried. Slashdot fails to have the Slashdot Effect on LJ. LJ is thriving and functional thanks to the developers who put it together and the engineer-types who keep it running day-to-day and the people who keep the money coming in to feed the monster bandwidth and all the rest of it, and the people who make sure that other people know how to use it, and the people who stay here and hang out and talk with friends. The developers work hard to keep things working and keep the site evolving so it doesn't become a great big code dinosaur. Lately it's been seeming that the harder they work to fix things that are broken and update things that are out of code (building code metaphor, not computer code; work with me here), the more they get screamed at for trying to ruin LJ.
In every
news feature-type post where something new and bell/whistle is announced, there is the inevitable complaint that things like virtual gifts are a waste of developer time that would be better spent on problem X, Y, or Z. And when LJ has been having a couple weeks where there are problems, and the problems stay there even though people are complaining about them, and the problems are still there, and still there, and still there -- yes, it does seem illogical that developers would go and do something like make it possible to put a flaming bag of poo on your least favorite serial adder's profile page. But sometimes you have to step away from a problem to get it back in perspective. I'm not in LJ Central, so I'm not there watching them bang their heads into a stubborn problem until headaches ensue, but I trust that they are allocating their time reasonably.
You know what I think the number one biggest waste of developer time is?
Dealing with unaccountably rude and hostile users.
LJ as a culture has the hugest sense of fandom entitlement ever.
LJ users want the same thing they've always had from LJ, namely, a place to put their journals and communicate and be with friends, and a geek-friendly, open, caring, open-source, user-supported, small-town environment.
LJ geeks want pretty much that same thing. Really. Truly.
Somewhere along the line, LJ users as-a-collective got the idea that if the development team did something that they didn't like, the best way of solving this was not to give constructively critical feedback and debate it with vigor and the knowledge that the developers had the good of the site in mind, but to jump on any available surface and flame away.
Imagine the utter fucking joy that the LJ developers must be having, wading through gods know how many hundred comments of flame to find the legitimate kernels of actual problems in between the complaints. Go through one of those posts announcing changes to LJ some time, and pretend that the changes to LJ are a fic that's already been beta-read, and the comments to those posts are comments in response to the fic. Read those comments with an eye to constructive criticism. The analogy doesn't stretch particularly far, because the core site pages of LJ are not a piece of fanfiction, but the principle of effective communication holds true.
Dear users, the way to get the development team to listen to your concerns is not to scream abuse at them and then expect them to abandon their ideas of what is right for the site and adopt yours. The louder you scream, the louder they're going to hit the delete key and say "Na na na can't hear you na na na." I don't actually think they're doing that now, but the temptation is very much there and very much real. LJ is a maverick site in that it has such open forums for user feedback and discussion. Plenty of services do not have anything resembling that. Do you really want to convince the developers and volunteers that an open forum will only collect whining and flames?
Hint: Bantown tried forcing the issue by attacking LJ. We all know how that turned out. Pwned, craxx0rbitches, pwned. In a similar case, visible nipple is still not allowed in the default userpic, and the flaming tantrums thrown at LJ's support staff by assorted self-proclaimed "boob nazis" have assured that visible nipple will never be allowed, on the principle that it's bad precedent to cave when the toddler has a meltdown because they didn't get their little way. Even though there are many people who do love the boob.
Tell them what you like about the shiny new stuff. Let them know what they did right. Sit on your hands for a few hours until you try using it a few times before you flame off at them. If you have to say something immediately, remember what you learned in those sensitivity training sessions and use your "I" statements. "I'm frustrated with this new user interface, and I'd really prefer something with the look and feel of the older version" comes over a whole lot better than "What the fuck did you do to my user interface, you morons? I liked it the way it was! Put it back!"
LJ, even current LJ under 6A management, is capable of recognizing if something goes really badly. The developers actively ask for reports of broken or unusable behavior. Things may not be fixed immediately, but there are little things coming out every here and there to make things better, things that you may not be aware of unless you're watching
lj_releases or
changelog.
LJ really is a group effort. I do not have Super-Secret Inside Information that no one else has. I'm a relatively average occasional Support volunteer. (Very occasional, since Life Attacks.) I put time and effort into making LJ a better place, and I see the results of that effort. Things may not always go my way when LJ policy and I disagree with each other (I wouldn't mind seeing nipples in any boobtacular default user pictures, for example), but at least my technical suggestions are often dead-on, and my social suggestions are at least listened to respectfully.
I really do think it all boils down to three or four questions:
And you know? I find that I'm never short on database handles after this update. How about you?
I will do my best to make the feedback I leave for LiveJournal developers constructive in nature.
If you wouldn't do it in fandom, don't do it to the devs. I know that this is the choir section here that I'm ranting at, but I've spent the past couple hours in a room with some rather irritated engineers who are really code people, not people-people. They've been busting their asses for months to track down random crap that goes wrong. This site is so bloody huge and robust that Bantown could not take it down for long, even though they tried. Slashdot fails to have the Slashdot Effect on LJ. LJ is thriving and functional thanks to the developers who put it together and the engineer-types who keep it running day-to-day and the people who keep the money coming in to feed the monster bandwidth and all the rest of it, and the people who make sure that other people know how to use it, and the people who stay here and hang out and talk with friends. The developers work hard to keep things working and keep the site evolving so it doesn't become a great big code dinosaur. Lately it's been seeming that the harder they work to fix things that are broken and update things that are out of code (building code metaphor, not computer code; work with me here), the more they get screamed at for trying to ruin LJ.
In every
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
You know what I think the number one biggest waste of developer time is?
Dealing with unaccountably rude and hostile users.
LJ as a culture has the hugest sense of fandom entitlement ever.
LJ users want the same thing they've always had from LJ, namely, a place to put their journals and communicate and be with friends, and a geek-friendly, open, caring, open-source, user-supported, small-town environment.
LJ geeks want pretty much that same thing. Really. Truly.
Somewhere along the line, LJ users as-a-collective got the idea that if the development team did something that they didn't like, the best way of solving this was not to give constructively critical feedback and debate it with vigor and the knowledge that the developers had the good of the site in mind, but to jump on any available surface and flame away.
Imagine the utter fucking joy that the LJ developers must be having, wading through gods know how many hundred comments of flame to find the legitimate kernels of actual problems in between the complaints. Go through one of those posts announcing changes to LJ some time, and pretend that the changes to LJ are a fic that's already been beta-read, and the comments to those posts are comments in response to the fic. Read those comments with an eye to constructive criticism. The analogy doesn't stretch particularly far, because the core site pages of LJ are not a piece of fanfiction, but the principle of effective communication holds true.
Dear users, the way to get the development team to listen to your concerns is not to scream abuse at them and then expect them to abandon their ideas of what is right for the site and adopt yours. The louder you scream, the louder they're going to hit the delete key and say "Na na na can't hear you na na na." I don't actually think they're doing that now, but the temptation is very much there and very much real. LJ is a maverick site in that it has such open forums for user feedback and discussion. Plenty of services do not have anything resembling that. Do you really want to convince the developers and volunteers that an open forum will only collect whining and flames?
Hint: Bantown tried forcing the issue by attacking LJ. We all know how that turned out. Pwned, craxx0rbitches, pwned. In a similar case, visible nipple is still not allowed in the default userpic, and the flaming tantrums thrown at LJ's support staff by assorted self-proclaimed "boob nazis" have assured that visible nipple will never be allowed, on the principle that it's bad precedent to cave when the toddler has a meltdown because they didn't get their little way. Even though there are many people who do love the boob.
Tell them what you like about the shiny new stuff. Let them know what they did right. Sit on your hands for a few hours until you try using it a few times before you flame off at them. If you have to say something immediately, remember what you learned in those sensitivity training sessions and use your "I" statements. "I'm frustrated with this new user interface, and I'd really prefer something with the look and feel of the older version" comes over a whole lot better than "What the fuck did you do to my user interface, you morons? I liked it the way it was! Put it back!"
LJ, even current LJ under 6A management, is capable of recognizing if something goes really badly. The developers actively ask for reports of broken or unusable behavior. Things may not be fixed immediately, but there are little things coming out every here and there to make things better, things that you may not be aware of unless you're watching
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
LJ really is a group effort. I do not have Super-Secret Inside Information that no one else has. I'm a relatively average occasional Support volunteer. (Very occasional, since Life Attacks.) I put time and effort into making LJ a better place, and I see the results of that effort. Things may not always go my way when LJ policy and I disagree with each other (I wouldn't mind seeing nipples in any boobtacular default user pictures, for example), but at least my technical suggestions are often dead-on, and my social suggestions are at least listened to respectfully.
I really do think it all boils down to three or four questions:
- Do you trust the people who are running LJ, including Six Apart core and the developers?
- If you do not trust the people running LJ, what can they reasonably do to demonstrate that they're worthy of your trust?
- If there is nothing the people running LJ can do to gain your trust, why are you still here?
And you know? I find that I'm never short on database handles after this update. How about you?
no subject
Fine tuning dialogues that work well is a classic programmer behavior. "This must be PERFECT!" is the thought, so they're going to fiddle until it meets their aesthetic ideal. Meanwhile there's other tasks--less fun ones--which are lying undone even though they'd contribute more to user satisfaction. Or there should be. If rearranging the text fields in the update screen is actually the most important thing on the development team's to-do list they need to step back, proclaim LJ finished, and start something totally new. Something whose worth will justify the value of the programmer hours put into it.
On a more practical note, is there a PO Box for the dev team? I'm tempted to send them copies of Peopleware and The Inmates are Running the Asylum as references.
no subject
Neither, however, do I bother ranting and screaming. Not any more. :P
no subject
They are combining the openID logins and RSS feeds for vox/LJ friendings, and that's one of the things that got partially explored in
no subject
no subject
(no subject)
(no subject)
no subject
And it took a heck of a lot of effort to get a suggestion through about the security hole in the notifications system, -- since one way to fix it would be to NOT automatically unscreen comments I was gettign rejected as already suggested. Feh.
no subject
[email protected]
with your thoughts on the matter."(no subject)
no subject
no subject
if you'd like to, go right ahead.
and after reading the entry, you already commented on it! XD
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
Sure, you can address that with documentation. You can put little pop-up inline help bubbles everywhere -- I'm staring at two of them right now writing this comment. You can write tutorials. You can do a whole lot of things. But there comes a point where you have to just bite the bullet and redesign your site to stop hiding critical paths and frustrating your users.
It doesn't seem like a priority to existing LJ users, especially the power users, because they've already figured it out and it's second nature to them; to them, it looks like rearranging the deck chairs on the Titanic. But we have hard, fast evidence that indicates that with the update page redesign, our taskflow abandonment rate dropped from something crazy like 80% to something far more sane like 30%. (I'm pulling these numbers out of my ass, since I don't feel like logging into the stats server right now, but it was a HUGE drop like that.)
So, because we can't release those stats and those figures -- to do so would be like inviting our competition to come wandering in behind the scenes and shaft us -- it looks like we're just arbitrarily deciding to change shit. We're really not. I swear to you. There's no way we'd have put priority on something like that if it were developer whim. We're way, way better managed than that. Everything aesthetically unpopular over the past six months -- the navstrip, contextual hover menus, redesigning the update page, changing the site scheme, the profile redesign, etc, etc -- has been designed for one purpose and one purpose only: to fix some statistic or another that fucking scares us, because it implies bad things for the long-term health, stability, and viability of the site.
Also, you've gotta remember -- we have two sets of engineers, front-end and backend. Having one of our frontend engineers working on redesigning the update page doesn't take time away from the guy who's working on, say, journal search -- the two positions have very, very few overlapping skillsets, and if the guy working on the update page redesign wasn't working on that, he'd be working on some other form of user interface.
no subject
The CProds? The fact that one of the LJDesign people got up in one of the anti-ad comms and said that we should not be allowed to turn them off hacked a lot of people off.
I understand what you are saying about task abandonment rates. But I'm not seeing the reason for making some of these optional changes opt-out. If it's optional, it should be opt-in. If it's not optional, don't pretend that it's optional?
Does that make sense?
Also, with regards to the virtual gifts? I really don't like the idea that people who don't like me can pay you to put things on my profile that I didn't ask for and don't want and can do so without giving their names. I'm someone who has a lot of fans and a lot of foes online, and someone actually DID pay to put a flaming bag of poo on my profile anonymously. I think the option for anonymous gifting should at the very least be restricted to the unambiguously NICE gifts, and yes, I'm annoyed that even though I set my journal up so that no-one can comment anonymously or do anything else anonymously, they can still put a flaming bag of poo in my userinfo anonymously. I'll say that here, because Azz is a friend, but I won't say that in public, because the person who did it might read it and have the satisfaction of knowing that it pissed me off.
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
Plug ins'n'outs
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
Belated reply due to holidays
Re: Belated reply due to holidays
Re: Belated reply due to holidays
Re: Belated reply due to holidays
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
... post to something like
no subject
So now I have it disabled via Greasemonkey.
no subject
I have to second the Vgift issue as well. I have gotten quite a few anonymous gifts (poo bags, coal lumps) with harassing messages attached. They sit on my profile page all day until I get home from work and can remove them. And I have no way to stop them. The last one I received was on - you guessed it - the day the latest newspost was made announcing new Vgifts, before I had even had a chance to see the newspost.
When Vgifts was first introduced, people said that it could and would be abused. Staff said that being able to delete gifts after the fact should be good enough, but it's not.
no subject
So instead let me strongly suggest getting a copy of Alan Cooper's book on interaction design. (http://www.amazon.com/Inmates-Are-Running-Asylum-Products/dp/0672326140/sr=1-1/qid=1166458314/ref=sr_1_1/103-2025606-3515834?ie=UTF8&s=books) Despite the flame-bait title it's a very good overview of how to design software for usability at the architecture level. Tinkering at the lower level can't fix problems caused by the top level design. The best way to use the book may be to get two programmers from each team to read it and then get together for a brainstorm of "how should this work?"
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
The new update page, though, confuses me every time I post to a community: I get to the end of the post, go "argh, where's the 'change journal' option?", remember, scroll back up to the top of the page, realise I wanted to add a tag, scroll back down.... Plus, the huge font is horrible, and keeps scaring me into thinking I'm somehow stuck in bloody rich text mode.
Yes, the power users already figured it out. Yes, the power users just decided that it was easier to add /poll/create.bml? to the url. And, yes, the power users are more likely to figure out the way to get around the new changes with the least hassle: just because they aren't showing up on site stats as reaching a dead end and giving up doesn't mean that they aren't finding it really bloody hard work to deal with. The non-power users, who've gradually figured out how LJ works over a period of time, are even more stuffed by it, because they're not only having to re-learn stuff but they're also not so able to figure out the new optimal path on the fly.
I appreciate that "people who've been around and would leave if it weren't for the fact that they've been around for so long" aren't a significant percentage of your users, and that (as many of them are perm members) they also aren't a significant percentage of your income stream (and must be really horrible, now, from a cashflow persepective), but they do exist. Beta access to New Stuff is nice. Consideration would be nicer.
Anyway: sorry, got here via a link. Sorry to
no subject
no subject
no subject
This is the sort of non-flaming, critical discussion that I wish got started in the official communities.
no subject
[I sometimes think nothing useful ever happens through official channels, they're just there to provide context for the backchannels]
no subject
The level of literacy and command of the language on the Bujold list really spoiled me for most of the rest of the Internet.
no subject
This sums it up perfectly, it really does. I cannot understand why the LJ team cannot see this for themselves, I really can't.
'If it ain't broke, don't fix it', might be something of a cliche and joke, but it's also darn true.