![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Jul. 5th, 2006 08:47 pmWell, still no word from the people with whom i talked last Wednesday, although their HR person said she'd know something by Friday. I'm guessing that perhaps someone from whom feedback was needed took a long holiday weekend. Regardless, i'm not particularly concerned, and if i'm supposed to make a move, when the time is right the opportunity will present itself. At least in the present situation, i'm finally getting to work toward defining process- or what it should be.
Had an interesting chat with a co-worker today who told me that i basically need a maintenance team- a developer and a tester who can fix the little things which get reported as broken but which the main product group teams don't have time to fit into their schedules. What an amazing concept- and when i did work with such a team, it kicked ass and got things accomplished. As it is now, i fix lots of data problems and contribute a few lines of C# once in a blue moon because my 'customers' as the manager of software release are all the users of the website, and their interests and needs aren't being met by having to wait a month for trivial fixes.
I'm technically not supposed to make database modifications. I'd really rather not feel that i have to- but usually by the time i've run a problem down sufficiently enough to know what it is, i have a detailed SQL query which traces what the software does to retrieve data and which tells me pretty much what's wrong. Since what's usually involved is updating a value which for some reason didn't get properly entered, it doesn't make sense to spend all that time isolating the problem only to have to involve someone else— and take him (at this point, all the DB folk are male) away from whatever project he's working on to execute an update statement which takes fractions of a second. If i have any doubt, i don't do it, but seek advice from one of the pros. From having talked with them, they appreciate not being interrupted for trivial matters.
Had an interesting chat with a co-worker today who told me that i basically need a maintenance team- a developer and a tester who can fix the little things which get reported as broken but which the main product group teams don't have time to fit into their schedules. What an amazing concept- and when i did work with such a team, it kicked ass and got things accomplished. As it is now, i fix lots of data problems and contribute a few lines of C# once in a blue moon because my 'customers' as the manager of software release are all the users of the website, and their interests and needs aren't being met by having to wait a month for trivial fixes.
I'm technically not supposed to make database modifications. I'd really rather not feel that i have to- but usually by the time i've run a problem down sufficiently enough to know what it is, i have a detailed SQL query which traces what the software does to retrieve data and which tells me pretty much what's wrong. Since what's usually involved is updating a value which for some reason didn't get properly entered, it doesn't make sense to spend all that time isolating the problem only to have to involve someone else— and take him (at this point, all the DB folk are male) away from whatever project he's working on to execute an update statement which takes fractions of a second. If i have any doubt, i don't do it, but seek advice from one of the pros. From having talked with them, they appreciate not being interrupted for trivial matters.
