Excruciating waste of a morning
-
Just spent the morning fixing broken builds, broken by a colleague of mine. Yesterday in my absence she decides working builds are wrong, screws around with the build and reference configurations, then goes home for the evening with all our builds red. Before I even sit down she's at my desk, expecting the builds to be fixed because she "can't work any more". She then can't remember which configs or projects she edited, just that "they have to work again", leaving me to fix everything because she doesn't know what she's doing anyway. If you don't know what you're doing, what prompted you to start messing around with working builds in the first place? What sense of responsibility allowed you to go off home having just wrecked the nightly builds? As a rule I don't go to our development manager to complain about people but this is pushing my patience.
-
Just spent the morning fixing broken builds, broken by a colleague of mine. Yesterday in my absence she decides working builds are wrong, screws around with the build and reference configurations, then goes home for the evening with all our builds red. Before I even sit down she's at my desk, expecting the builds to be fixed because she "can't work any more". She then can't remember which configs or projects she edited, just that "they have to work again", leaving me to fix everything because she doesn't know what she's doing anyway. If you don't know what you're doing, what prompted you to start messing around with working builds in the first place? What sense of responsibility allowed you to go off home having just wrecked the nightly builds? As a rule I don't go to our development manager to complain about people but this is pushing my patience.
Today's lesson children is "Why should the build config be kept under source control"
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Today's lesson children is "Why should the build config be kept under source control"
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Just spent the morning fixing broken builds, broken by a colleague of mine. Yesterday in my absence she decides working builds are wrong, screws around with the build and reference configurations, then goes home for the evening with all our builds red. Before I even sit down she's at my desk, expecting the builds to be fixed because she "can't work any more". She then can't remember which configs or projects she edited, just that "they have to work again", leaving me to fix everything because she doesn't know what she's doing anyway. If you don't know what you're doing, what prompted you to start messing around with working builds in the first place? What sense of responsibility allowed you to go off home having just wrecked the nightly builds? As a rule I don't go to our development manager to complain about people but this is pushing my patience.
And this is why source control has rollback and blame built right into it.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
They already are. What we're dealing with here is a stultifying lack of initiative and responsibility.
jim lahey wrote:
a stultifying lack of initiative
On the contrary, she showed a lot of initiative, it was just totally misplaced. Years ago we had a guy on our development team who was (supposedly) working on a fix to a module. When release date was approaching the dev manager came to see him, and the conversation went something like: DM: Will the fix be fully tested by Friday? Dev: Er, well no, it may be a bit late. DM: So what's the problem. Dev: Well I didn't like the way that module was coded so I decided to re-write it. DM: OK, so when will it be ready. Dev: Well I haven't managed to get my re-write to compile yet ... The developer was invited to leave the team, and the company shortly afterwards.
One of these days I'm going to think of a really clever signature.
-
jim lahey wrote:
a stultifying lack of initiative
On the contrary, she showed a lot of initiative, it was just totally misplaced. Years ago we had a guy on our development team who was (supposedly) working on a fix to a module. When release date was approaching the dev manager came to see him, and the conversation went something like: DM: Will the fix be fully tested by Friday? Dev: Er, well no, it may be a bit late. DM: So what's the problem. Dev: Well I didn't like the way that module was coded so I decided to re-write it. DM: OK, so when will it be ready. Dev: Well I haven't managed to get my re-write to compile yet ... The developer was invited to leave the team, and the company shortly afterwards.
One of these days I'm going to think of a really clever signature.
Granted, she started some stuff on her own, but then dropped it and ran a mile when it broke and didn't even bother to ask the correct person who sits 5 feet from her to help fix it. Instead it's automatically my fault because it's my VS Solution.. WTF? Initiative is not just about starting stuff, it's also about being able to carry stuff out and getting the right help if you're stuck. I had to ask the guy who sits next to her and got my answer within 2 minutes. I didn't waste my time and others' time trying to apportion blame for my own WTF. Rest assured there is already a training session scheduled at my request for all team members about how to use the build server correctly, and if you don't know, ask.
-
Granted, she started some stuff on her own, but then dropped it and ran a mile when it broke and didn't even bother to ask the correct person who sits 5 feet from her to help fix it. Instead it's automatically my fault because it's my VS Solution.. WTF? Initiative is not just about starting stuff, it's also about being able to carry stuff out and getting the right help if you're stuck. I had to ask the guy who sits next to her and got my answer within 2 minutes. I didn't waste my time and others' time trying to apportion blame for my own WTF. Rest assured there is already a training session scheduled at my request for all team members about how to use the build server correctly, and if you don't know, ask.