![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Aug. 11th, 2005 09:36 pmTired. Annoyed.
Tomorrow, we push our project to beta. We had a walk-through with some of the people who will be showcasing it next week and the executive vice-president who heads marketing today, and in the latter's words, "You guys hit a home run with this. For [publishing person] to have said that she thinks that she could use it is a huge win just underscores it, because she's not a technical person at all."
It's not all golden laurels, though.
Seems prima-donna developer boy tried to get D-Lo to deploy to beta tonight. I'm going to have words with him tomorrow. Specifically these ones: "You're a developer. You write code. I'm a tester. I okay deploying code when i'm certain that it's functional enough for what it needs to do. You don't request deployments, i won't write crappy code." Since it's going to beta, and for a limited audience, i don't really have a problem releasing it as is, with known issues. Currently, there's one known issue which is blocking test of areas subsequent to it— activation needs to happen before committment, and![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
lokheed's reset functionality is contingent upon having committed values (or at least the documentation on it says that it is, and i can't believe that it's non-functional). It works well enough in test that we can let the business-folk play with it and show off some of what it'll do, but ncontrol has been given a pretty good idea of what should work and what probably won't, and she's showing everything with the caveat that we're just feature-complete, not ready for deployment yet but in good enough shape to get general feedback and get tested.
I'm starting to wonder if prima-donna boy is really that clueless or has that little respect for process, or if he really and truly gets off on being as difficult to work with as possible. I'm leaning toward the latter. It'd be an easy explanation for a number of his passive-aggressive traits.
Tomorrow, we push our project to beta. We had a walk-through with some of the people who will be showcasing it next week and the executive vice-president who heads marketing today, and in the latter's words, "You guys hit a home run with this. For [publishing person] to have said that she thinks that she could use it is a huge win just underscores it, because she's not a technical person at all."
It's not all golden laurels, though.
Seems prima-donna developer boy tried to get D-Lo to deploy to beta tonight. I'm going to have words with him tomorrow. Specifically these ones: "You're a developer. You write code. I'm a tester. I okay deploying code when i'm certain that it's functional enough for what it needs to do. You don't request deployments, i won't write crappy code." Since it's going to beta, and for a limited audience, i don't really have a problem releasing it as is, with known issues. Currently, there's one known issue which is blocking test of areas subsequent to it— activation needs to happen before committment, and
lokheed's reset functionality is contingent upon having committed values (or at least the documentation on it says that it is, and i can't believe that it's non-functional). It works well enough in test that we can let the business-folk play with it and show off some of what it'll do, but ncontrol has been given a pretty good idea of what should work and what probably won't, and she's showing everything with the caveat that we're just feature-complete, not ready for deployment yet but in good enough shape to get general feedback and get tested.I'm starting to wonder if prima-donna boy is really that clueless or has that little respect for process, or if he really and truly gets off on being as difficult to work with as possible. I'm leaning toward the latter. It'd be an easy explanation for a number of his passive-aggressive traits.
