Other than that, reports/status "at the detail level" are extremely important.
It's those 'little details' that haven't being working.
My point is that status reports don't fix them. Work fixes them. I'm not going to ask the programmers to tell me when each of the problems will be fixed because it would be a waste of their time which is better spent fixing the problems.
"The first two you're reporting are actually the same problem. Fix one and the other is fixed."
No Bob, they were not the same problem. Not at all.
Please tell me how they are different, then. Based on my understanding of how the system works, they are the same problem; just two different symptoms of the same problem, which I believe is treating message-numbering as being one-based when it's actually zero-based.
Your understanding of the inner workings of the site might be better (I've only seen the old site's source code, not the new site's), and if they are indeed two separate problems, please give me the details. I've only reported that as one problem and may've left out an important one the programmers need to know about.
Sorry I even posted you about it.
Posted to the wrong person obviously.
I'm sorry you feel that way. I've been a sort of defacto liaison between the community and the programmers, reporting problems in clear, concise geek-speak (which they can work better with), so I'm not really a bad choice for conveying problems to them. It works anyway.
If you're looking for detailed status reports and anticipated timeframes, then I'm the wrong person. I'm not sure who the right person is.
If you're reporting problems with the site, you're posting to the right person.
Regards,
SI Admin (Bob) |
