(no subject)
Jul. 18th, 2002 03:40 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ravencallscrowsI've come to the conclusion that my boss is a complete and total fuck-wit. Actually, i've known that for quite some time, but just re-confirmed it again today.
During my weekly meeting with him, the build analysis reports came up. He now wants to add analysis of admin images to them. Not a problem, it just means that now i have to create admin images for the major releases and then compile file lists for each of them. Figure that's another twenty minutes apiece there to get that done, so that adds another hour to the chore. Never mind that by analyzing the build itself we have a more complete and thorough listing of all the files, including things like merge modules (where bugs can easily hide), if he wants those lists, he'll get those.
His second comment about the reports: "These are just raw data. I don't want just the data, I want conclusions. I want to know what changed from build to build or from Arabic to English."
Know what, fuck-wit? Look at the data. The spreadsheet lists every file change, and every way Arabic builds are different than English ones. You want conclusions? OK. 334 files changed between the last two Arabic builds, 262 between the last two English ones, all of which are either in the changes for the Arabic or there's a valid reason why they're not. If there were other changes, there'd be bugs logged about them. Tracking individual file changes makes sense when you're locking a product down getting it ready to ship, but when you have more than two dozen or so changes, there's too much to report to be newsworthy, but making these damn lists and verifying that the 262 English changes are either also in Arabic or have a good reason not to be is enough work in itself without needing to also write a summary saying that there's nothing to report.
Oh, yes. I'm also supposed to write less in reports and e-mail, summarizing things to bullet-points, but also supposed to supply detailed analysis for every task i do.
I'm also supposed to spend "more time focused on finding quality bugs" while not protesting when my time is occupied compiling meaningless reports.
I'm an unsatisfactory employee, suddenly, but i'm so vital to the team i won't be released to interview for jobs in other groups or departments.
No one else on the team has any sort of visible "deliverables" on a per build basis like these damn reports, but it's essential that i publish them and that they take top priority when builds come out.
Is it just me, or does there seem to be a bit of a double-standard here? It's pretty evident that having mutually contradictory expectations leaves me in pretty much a no-win situation.
During my weekly meeting with him, the build analysis reports came up. He now wants to add analysis of admin images to them. Not a problem, it just means that now i have to create admin images for the major releases and then compile file lists for each of them. Figure that's another twenty minutes apiece there to get that done, so that adds another hour to the chore. Never mind that by analyzing the build itself we have a more complete and thorough listing of all the files, including things like merge modules (where bugs can easily hide), if he wants those lists, he'll get those.
His second comment about the reports: "These are just raw data. I don't want just the data, I want conclusions. I want to know what changed from build to build or from Arabic to English."
Know what, fuck-wit? Look at the data. The spreadsheet lists every file change, and every way Arabic builds are different than English ones. You want conclusions? OK. 334 files changed between the last two Arabic builds, 262 between the last two English ones, all of which are either in the changes for the Arabic or there's a valid reason why they're not. If there were other changes, there'd be bugs logged about them. Tracking individual file changes makes sense when you're locking a product down getting it ready to ship, but when you have more than two dozen or so changes, there's too much to report to be newsworthy, but making these damn lists and verifying that the 262 English changes are either also in Arabic or have a good reason not to be is enough work in itself without needing to also write a summary saying that there's nothing to report.
Oh, yes. I'm also supposed to write less in reports and e-mail, summarizing things to bullet-points, but also supposed to supply detailed analysis for every task i do.
I'm also supposed to spend "more time focused on finding quality bugs" while not protesting when my time is occupied compiling meaningless reports.
I'm an unsatisfactory employee, suddenly, but i'm so vital to the team i won't be released to interview for jobs in other groups or departments.
No one else on the team has any sort of visible "deliverables" on a per build basis like these damn reports, but it's essential that i publish them and that they take top priority when builds come out.
Is it just me, or does there seem to be a bit of a double-standard here? It's pretty evident that having mutually contradictory expectations leaves me in pretty much a no-win situation.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2002-07-18 05:32 pm (UTC)