Newsfiend
01-27-2010, 03:20 PM
wizdons wrote:
Aristo wrote:
wizdons wrote:
a response is different than a commitment to fixing it.
Mind if I quote this?
See you took the time to read this and try and make a funny, but wont take the time and respond to other real problems.
Fixed the spelling anyway..
Well, let's see what we've been doing:
Working on prioritized tasks
Fixing bugs with content we own
Fixing bugs we can fix without input in content we don't own
Tracking down systemic bugs and determining if they are related to code, design, operations, or a combination of them
Working on new content to meet our schedules for future releases
Discussing problems with the team when it requires more than one person's input
Working on documents for content you don't know about yet
Here's what we haven't been doing:
Changing things in content or systems we don't own
Posting about content or systems we don't own
Posting about changes when we don't know what those changes will be
Posting when there's no insight or answers we can offer
Posting when we have more pressing priorities
Fun fact: Of the last 100 bugs closed in our tracker, 75 are for content that hasn't been released yet.
Fun fact: The time I've spent writing this response means I'm spending extra time in the office tonight.
Fun fact: Posting and working are mutually exclusive, and when we go 'dark' like this it's not because we're twiddling our thumbs and looking for things to do.
More... (http://forums.station.sony.com/eq/posts/list.m?topic_id=160493&post_id=2386564#2386564)
Aristo wrote:
wizdons wrote:
a response is different than a commitment to fixing it.
Mind if I quote this?
See you took the time to read this and try and make a funny, but wont take the time and respond to other real problems.
Fixed the spelling anyway..
Well, let's see what we've been doing:
Working on prioritized tasks
Fixing bugs with content we own
Fixing bugs we can fix without input in content we don't own
Tracking down systemic bugs and determining if they are related to code, design, operations, or a combination of them
Working on new content to meet our schedules for future releases
Discussing problems with the team when it requires more than one person's input
Working on documents for content you don't know about yet
Here's what we haven't been doing:
Changing things in content or systems we don't own
Posting about content or systems we don't own
Posting about changes when we don't know what those changes will be
Posting when there's no insight or answers we can offer
Posting when we have more pressing priorities
Fun fact: Of the last 100 bugs closed in our tracker, 75 are for content that hasn't been released yet.
Fun fact: The time I've spent writing this response means I'm spending extra time in the office tonight.
Fun fact: Posting and working are mutually exclusive, and when we go 'dark' like this it's not because we're twiddling our thumbs and looking for things to do.
More... (http://forums.station.sony.com/eq/posts/list.m?topic_id=160493&post_id=2386564#2386564)