|eng vs. designers vs. ops vs. biz
||[Mar. 21st, 2006|11:30 am]
.... it's funny to imaigne a service if A) engineers made all the decisions, B) designers made all the decisions, C) ops made all the decisions, D) business made all the decisions
A) hilariously complicated, billions of features
B) no features, like 1 button
C) static html page
D) blinking ads all over that spam you if you look at them
2006-03-21 09:18 pm (UTC)
what is wrong with static html
Certainly save some time on keeping service up during scheduled maintenance...
"C" would actually be "ovens for users, firing squads for A, B and D."
We just want to avoid problems down the road.
... and enjoy getting paid to do nothing.
What about engineers who are good at design?
One hilariously complicated button.
There are solutions:
A. You get paid the same whatever features it has and can spend any free time on open source projects.
B. OK, I admit it, this one can't be solved. Just shoot the designers.
C. Pay ops people commission per incident and use the level of incidents to decide how many ops people are needed, fewer incidents. more people get fired.
D. This is tough. Hand over the advertising program to an intern and reward them on the basis of community acceptance. Intern must have extensive work experience with an ad blocking company. No ads until a suitable intern can be found.
Oh shit! Is that why I have such a tough time getting promoted? ;)
Are you sure it's not because of the way you smile at motherboards, daughtercards and female sockets?
Okay, I was going to say something racist about Sun equipment vs beigeboxes, but I'll just stop here.
E) Abuse made all the decisions: website remains the same except for the mysterious dissapearance of the create.bml page