posted by ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
giogio at 11:00am on 04/08/2007
giogio at 11:00am on 04/08/2007So now everyone is having kittens about this and particularly, it seems, for LJ having what amounts to a (presumably documented) QC procedure to determine whether something is a violation of the TOS...
Allow me to use another manufacturing analogy, because I think it's actually a good one. Essentially blogging is all about "manufacturing" content.
So, say we were part of a company manufacturing cars.
As we were designing the car, our engineers would go all for teh pretty and the cool functions, our purchasing agents would have kittens about using cheaper product to achieve something resembling what the engineers were dreaming up, our business development department would scream that we would alienate male customers by making the whole thing bright purple, our QA department would get right into the middle of it and yell at length about engineering and purchasing both being insane trying to spec/purchase that particular brake manufacturer accompanied by the lawyers screaming about liability, and senior management would have serious concerns about being named as codefendants in any lawsuit resulting from the whole mess. And then the various departments would have to sit down and come up with a solution that would produce a marketable, reasonably priced, and safe car for the end consumer, and *nobody* would be 100% happy with the outcome, but it would be a car that would ultimately sell and limit our company's liability to the best of our abilities. And because we would have gone through the entire review process and documented it along the way, if the car were to blow up at a later date and somebody would sue, we could demonstrate due diligence and likely avoid criminal/gross negligence charges, and somewhat limit all other damages awarded by a court to the plaintiff.
It's a very sensible business decision, and, with all due respect, it actually demonstrates that LJ is trying to be a business entity in the long term.
And I totally need a professional hat icon.
Allow me to use another manufacturing analogy, because I think it's actually a good one. Essentially blogging is all about "manufacturing" content.
So, say we were part of a company manufacturing cars.
As we were designing the car, our engineers would go all for teh pretty and the cool functions, our purchasing agents would have kittens about using cheaper product to achieve something resembling what the engineers were dreaming up, our business development department would scream that we would alienate male customers by making the whole thing bright purple, our QA department would get right into the middle of it and yell at length about engineering and purchasing both being insane trying to spec/purchase that particular brake manufacturer accompanied by the lawyers screaming about liability, and senior management would have serious concerns about being named as codefendants in any lawsuit resulting from the whole mess. And then the various departments would have to sit down and come up with a solution that would produce a marketable, reasonably priced, and safe car for the end consumer, and *nobody* would be 100% happy with the outcome, but it would be a car that would ultimately sell and limit our company's liability to the best of our abilities. And because we would have gone through the entire review process and documented it along the way, if the car were to blow up at a later date and somebody would sue, we could demonstrate due diligence and likely avoid criminal/gross negligence charges, and somewhat limit all other damages awarded by a court to the plaintiff.
It's a very sensible business decision, and, with all due respect, it actually demonstrates that LJ is trying to be a business entity in the long term.
And I totally need a professional hat icon.
There are 2 comments on this entry. (Reply.)