JenLarkin
17 years ago
almost quit today.
latest #34
MoBarger
17 years ago
:-o
JenLarkin says
17 years ago
what I do not need right now is some cowboy risking the integrity of the builds across all but one of the client's servers
JenLarkin says
17 years ago
to do a change request two days before launch
立即下載
JenLarkin says
17 years ago
at the client said they could live without
JenLarkin says
17 years ago
instead of doing the security system work that he volunteered to do last week and hasn't done for fear of breaking the build
JenLarkin says
17 years ago
duplicating the work that I already had completed because he "found a bug"
JenLarkin says
17 years ago
edited the JS file that the UI team expressly forbade him to work on last week when he pulled crap like that
JenLarkin says
17 years ago
to put in a fix for the UI team that the UI guy started working on half an hour later only to find it done
JenLarkin says
17 years ago
putting changes into the repository that give me merge errors so I have to hand merge the files
JenLarkin says
17 years ago
removing validation code and the framework around it when the framework is right but the rules are wrong
JenLarkin says
17 years ago
which I already had in progress on my machine and now has to be hand merged
JenLarkin says
17 years ago
all because he wanted to close this stupid feature request that I loudly opposed because of the likelihood that it would break the build
JenLarkin says
17 years ago
so I now have to fix half a day's work, the build is probably broken for the India team
JenLarkin says
17 years ago
we have a database that is out of sync with the rest of the databases
JenLarkin says
17 years ago
and he is INSISTING that his changes are going to be ok for the India team
JenLarkin says
17 years ago
when his change was to change the datatype on a database column from numeric to text on only one of the 3 in use databases
Babyhellfire
17 years ago
would have quit
JenLarkin says
17 years ago
we have procedures and he broke most of them
JenLarkin says
17 years ago
and we have them because people kept doing crap like this and breaking everything
JenLarkin says
17 years ago
and he's being held up as being awesome and competent because he closes more bugs than I do
JenLarkin says
17 years ago
which he does because I TEST thoroughy
JenLarkin says
17 years ago
the thing that he changed-- to do a thorough test on it takes 30 minutes
JenLarkin says
17 years ago
you have to run ten test cases
JenLarkin says
17 years ago
for everything you want to test
JenLarkin says
17 years ago
I know that he didn't run 3 of them because he deleted the code that managed them
JenLarkin says
17 years ago
I am overworked and burnt out and stressed out and what I don't need is people fucking up the stuff I'm already working on
JenLarkin says
17 years ago
instead of implementing things that we need for the launch in 2 days that has to be turned over to another team when its done
MoBarger
17 years ago
I guess it that was happening to me I would document everything and point out the issues to the PM or the person running the project.
quetwo gives
17 years ago
Jen a hug
webRat says
17 years ago
When deadlines are that close, it's hard to document. Documentation is for people that have time. ;-) I would have gone and talked to PM
webRat says
17 years ago
And, perhaps asked him to call a meeting.
Kavka says
17 years ago
(angry) (cozy)
Lux
17 years ago
(doh) (angry)
dangrsmind
17 years ago
bad time to be unemployed, IMO
back to top