(no subject)
Feb. 10th, 2005 06:02 pmToday shifted gears from lethargic and slow paced to hectically busy in the course of a half-hour.
I haaaaaaaate the workflow of our new methodology. Of the three developers who code on my project, only
lokheed can be counted upon to unit test his code before checking it in or tell me when he's got something checked in that's ready to be tested. As for the other two, well, i ask two or more times a day, and still end up guessing what elements they've worked on.
As a result, it feels as if i waste large chunks of time just sitting and waiting. Fortunately, there are a fairly decent number of people who will keep me entertained during my downtime via one breed or another of instant messenger.
The Powers That Be want to release the first part of what we're doing shortly. Right now, 15 February is our release date. This is basically a UI overhaul of the last project i did (on which
lokheed was the developer), but the coding structure is migrating as well, so much of it is getting re-written. Unfortunately, they're tending to hit the same bits over and over again, so when there's something that's wrong on a page, there really isn't much purpose in me bugging it, because the chances are that it's just something they haven't finished implementing yet, so there really isn't a huge purpose in testing things while they're in flux.
But with a release date closing, they should be wrapping up. Or so i thought when i got a new build at 3:30ish today. After taking the time to deploy it and getting to field questions from our project business analyst, it was 4:00. In twenty minutes, i wrote six bugs, four of them what i'd consider showstoppers, one which can easily be deferred, and one just something which looks as if it's going to confuse the hell out of users. So- a big chunk of my tomorrow is meetings, Monday's scheduled to be more of the same, and since this will be the first integration since shifting to this half-assed implementation which leaves me with my doubts even if fully in place, after the code is integrated, i should probably regress the whole site, except that takes three testers six working days, and i'll be one tester who'll have one day and two partial days.
But work is the only less-than-positive thing in my life now, so, all in all, i still feel pretty damn good. Getting out last night helped a bunch
I haaaaaaaate the workflow of our new methodology. Of the three developers who code on my project, only
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
As a result, it feels as if i waste large chunks of time just sitting and waiting. Fortunately, there are a fairly decent number of people who will keep me entertained during my downtime via one breed or another of instant messenger.
The Powers That Be want to release the first part of what we're doing shortly. Right now, 15 February is our release date. This is basically a UI overhaul of the last project i did (on which
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
But with a release date closing, they should be wrapping up. Or so i thought when i got a new build at 3:30ish today. After taking the time to deploy it and getting to field questions from our project business analyst, it was 4:00. In twenty minutes, i wrote six bugs, four of them what i'd consider showstoppers, one which can easily be deferred, and one just something which looks as if it's going to confuse the hell out of users. So- a big chunk of my tomorrow is meetings, Monday's scheduled to be more of the same, and since this will be the first integration since shifting to this half-assed implementation which leaves me with my doubts even if fully in place, after the code is integrated, i should probably regress the whole site, except that takes three testers six working days, and i'll be one tester who'll have one day and two partial days.
But work is the only less-than-positive thing in my life now, so, all in all, i still feel pretty damn good. Getting out last night helped a bunch