azurelunatic: "My user interface is pastede on (yay)": scenes from an Access database that is not working so well.  (ui)
Azure Jane Lunatic (Azz) 🌺 ([personal profile] azurelunatic) wrote2006-12-15 02:29 am

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 [livejournal.com profile] 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 [livejournal.com profile] lj_releases or [livejournal.com profile] 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:
  1. Do you trust the people who are running LJ, including Six Apart core and the developers?
  2. If you do not trust the people running LJ, what can they reasonably do to demonstrate that they're worthy of your trust?
  3. 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?

[identity profile] rahaeli.livejournal.com 2006-12-18 07:38 pm (UTC)(link)
First off, just so you don't think this is some random Act of LJ Staff popping in or anything, I'm actually a friend of [livejournal.com profile] azurelunatic's -- I don't want to give the impression that I, like, monitor all of LJ to find people talking smack or what-have-you. I just happened to find this post as my Other Self. :) And I seem to be running off at the mouth here, so this is going to have to be multiple comments...

You pay LJ for services rendered, which is awesome of you and I appreciate it. On the other hand, though, your particular situation is an edge case; the "average" (median) paid user is a 24-year-old female with one account who updates between 5-10 times a month. The percentage of people with 2+ personal journals is very small; 3+ personal journals, you're down to a fraction of a percent (even when taken over active usage, not just total journals), and when you get to 10+ journals you're looking at -- well, I can't give numbers, but I'd call it a "handful". Which is not to say that your opinion counts for less, not at all -- just that your opinion has a greater chance, statistically, of being different than everyone else's opinion, because you're using LJ in a way that's less like the majority use.

And we don't want to create a product that can't appeal to both our hypothetical Annie Average and Emma Edgecase, but when we have to make a decision -- and we have to make decisions every day -- we need to consider what's going to serve the greatest good for the greatest number. And this isn't intended to be paternalistic at all, but to be completely, absolutely blunt: yeah, the people who are making the decisions know more about what's best for LiveJournal than you do, because they have access to more information -- usability studies, site workflow information, internal statistics, etc. They don't know what's best for your (or any one person's) personal use of LJ, because LJ users are an amazingly resourceful, adaptable bunch of people who have tweaked and fussed with the existing LJ resources into doing things they weren't intended to do (which, for the record, we think is immensely cool and we do, believe it or not, bend over backwards to avoid 'breaking' those uses). But they/we do have aggregate information that shows what effect changes have on the general usage of LJ as a whole -- which we can't publicly release, because it's the kind of thing our competition slavers over -- and decisions must be made on that big-picture level or else LJ risks tanking.

So we do something that's intended to fix a particular trend that frightens us (because it says bad things about long-term health and viability), but the most dedicated LJ users see it as a personal insult, because their use of LJ and their friends' use of LJ don't support the specific problem that we're trying to fix -- they just don't see it, because their particular circle uses LJ in a different way. And when we fix that problem, they see it as "messing with something that's not broken". Except it is 'broken' -- it's endangering LJ as a whole. So it looks to 'you' (generic 'you' here, not you specifically) like "LJ" decided to just fuck with something for the hell of it, while in actuality it's fixing a problem 'you' didn't even know about.

So then there's a huge outcry in [livejournal.com profile] news comments or what have you, with people objecting to the redesign/addition/revision/new feature/whatnot -- but there's also a quiet, mostly-invisible switch in the statistics and taskflow abandonment rate and usability/usage data that says, hey, that bad trend we were trying to fix has reversed itself. So now we're totally fucked no matter what we do; either we go back to the way things used to be (and watch those trends go right back to impending disaster), or look like we're ignoring user feedback. Or we take the path that we usually try to take: listen to all the feedback we get and implement the pieces that we don't think are going to have a negative impact on the stats.

[identity profile] ataniell93.livejournal.com 2006-12-20 04:39 am (UTC)(link)
I actually figured you were her friend.

I also understand about things like the update screen and the new site schemes. (Initially, I hated Horizon; now, I rather like it but I'm hoping for Vertigo soon, because I'm not such a fan of dropdown menus. Though, at least it doesn't require the precise mousing Xcolibur did. I loathed Xcolibur, I have RSIs.)

But those (except for the site scheme) are not opt-out anyway. I accept that the site will in fact make overall changes and golly gee whiz--most of them are good changes, too.

Where I get angry isn't because you changed the update screen to fix your task abandonment rate. I actually totally get that and...rather like the new update screen.

Here are *specific* things that have made me angry.

* The fact that when people were discussing the CProds and why they hated them in [livejournal.com profile] no_lj_ads, [livejournal.com profile] burr86 took it upon himself to tell me that I SHOULD NOT be allowed to turn them off and decide for myself whether I want to be told in a prod screen about every new feature (in each and every one of my accounts, too!) This actually inspired [livejournal.com profile] foxfirefey to write CSS that makes Firefox not display CProds, which I tested and Foxfirefey then distributed to anyone who wanted it, with loads of pimpage from me.

* The fact that in this same or a linked discussion [livejournal.com profile] winniewong thought it was funny that we were likening the CProds to Clippey and seemed to take pride in the fact that they annoyed the shit out of people.

* The unilateral decision, not once, but twice, to turn the Navigation Strip on for everyone, including the option which forces you to override other people's preferences. (Honestly, I can't think of any reason other than "to be annoying" why you would say to someone, "You can turn this thing off if you hate it, but we're going to let other people MAKE you look at it whether you hate it or not if THEY like it.") I had to turn that off in all the game journals because I don't believe that's right and I told my players they had to turn it off and they were having trouble finding it.

* The unilateral decision to autohide all birthday information even though the option to hide it had always been there and many of us had told LJ to display it please.

* The way that once LJ talk got turned on, suddenly all the other IM service information in most profiles was hidden unless you told it not to display LJ talk info (which I would never do even if I used LJ talk, because I don't put a working email address unmunged up anywhere on the internet nowadays).

I mentioned your brussels sprout comment as a particular irritant because it seemed to amuse you, just like Winnie Wong was amused by the furore over CProds. Here's a tip you and all the other developers could stand to take: when people are already annoyed over something you've done, smiling and laughing at their disgruntlement does NOT make them happier with you.