![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Post-Holiday Hangover?
Jan. 4th, 2005 04:07 pmToday: Ever so much so the work day from hell, only more, and in spades. No, make that No-Trump.
First: a breakthrough from one of my developers. This was the bright and shining moment of the day.
Then it was time to build with the new breakthrough. Except it wasn't. Our build engineer got sidetracked, and didn't get the build kicked off for about an hour.
In that time, someone complained about a structural change, which had been planned for weeks, and which was underpinning for the breakthrough change.
Rolling that change out broke the next build, and prevented the big change which was why it was requested in the first place from working.
[Insert much internal cross-talk here]
Finally, we reached the agreement that since the breakthrough bit was contingent on the framework change that it'd get put back, and that we'd build the stuff i need with it.
This process started at ten after nine this morning. It's now ten to four, and i still don't have a working build, so today's pretty much shot as far as getting this done. Oh yeah- and it ships next Thursday.
In other news, there are about a dozen different small projects in the works. No one wants to commit to prioritizing any of them so that releases (after next week) can be tentatively set. Instead, some genius wants to break all the ongoing work into little chunks and release weekly iterations. Unfortunately, the way things work around here, most elements are inter-related or have enough dependencies externally that making this work is going to be a challenge at best, assuming that everyone involved has developed pre-cognitive abilities and clairvoyance.
Agile development, my ass. In order for that to work, all of our developers would need to write unit testing before coding, and to the best of my knowledge, only one has done so. Oh- and everyone would have to communicate, if not live inside of each other's minds. And one more thing? It's rumoured that we're going to head back to having a team working on strategic projects and one working on maintenance items again- basically back where we were six months ago, when we were happy with the way things were going- so re-inventing the circle.
Oh- and while i've been writing this, the updated build, with the stuff i need checked back in failed bacause it was missing all sorts of references. There goes the rest of the day.
First: a breakthrough from one of my developers. This was the bright and shining moment of the day.
Then it was time to build with the new breakthrough. Except it wasn't. Our build engineer got sidetracked, and didn't get the build kicked off for about an hour.
In that time, someone complained about a structural change, which had been planned for weeks, and which was underpinning for the breakthrough change.
Rolling that change out broke the next build, and prevented the big change which was why it was requested in the first place from working.
[Insert much internal cross-talk here]
Finally, we reached the agreement that since the breakthrough bit was contingent on the framework change that it'd get put back, and that we'd build the stuff i need with it.
This process started at ten after nine this morning. It's now ten to four, and i still don't have a working build, so today's pretty much shot as far as getting this done. Oh yeah- and it ships next Thursday.
In other news, there are about a dozen different small projects in the works. No one wants to commit to prioritizing any of them so that releases (after next week) can be tentatively set. Instead, some genius wants to break all the ongoing work into little chunks and release weekly iterations. Unfortunately, the way things work around here, most elements are inter-related or have enough dependencies externally that making this work is going to be a challenge at best, assuming that everyone involved has developed pre-cognitive abilities and clairvoyance.
Agile development, my ass. In order for that to work, all of our developers would need to write unit testing before coding, and to the best of my knowledge, only one has done so. Oh- and everyone would have to communicate, if not live inside of each other's minds. And one more thing? It's rumoured that we're going to head back to having a team working on strategic projects and one working on maintenance items again- basically back where we were six months ago, when we were happy with the way things were going- so re-inventing the circle.
Oh- and while i've been writing this, the updated build, with the stuff i need checked back in failed bacause it was missing all sorts of references. There goes the rest of the day.
