How many of you...
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez This applies equally to those that check-in untested code, much less release it!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I must confess I've checked in non-compiling code once or twice... :-O And a couple of times that my checked in code didn't compile, but only because for some reason half of my code didn't get committed (like project A committed just fine, but project B didn't). And I've had a few coworkers who did that at least once a week which is very annoying. Or do you mean "release" as in a release to a customer? Because I can't imagine people not checking that :wtf:
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
I must confess I've checked in non-compiling code once or twice... :-O And a couple of times that my checked in code didn't compile, but only because for some reason half of my code didn't get committed (like project A committed just fine, but project B didn't). And I've had a few coworkers who did that at least once a week which is very annoying. Or do you mean "release" as in a release to a customer? Because I can't imagine people not checking that :wtf:
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Sander Rossel wrote:
Because I can't imagine people not checking that
You have to work on your imagination...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez This applies equally to those that check-in untested code, much less release it!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Shooting him is an act of mercy... I was in the line of skinning, boiling in oil... You know, the whole pack from the middle ages...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Sander Rossel wrote:
Because I can't imagine people not checking that
You have to work on your imagination...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Alright, perhaps I can imagine it. It was more like wishful thinking :-O
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
I must confess I've checked in non-compiling code once or twice... :-O And a couple of times that my checked in code didn't compile, but only because for some reason half of my code didn't get committed (like project A committed just fine, but project B didn't). And I've had a few coworkers who did that at least once a week which is very annoying. Or do you mean "release" as in a release to a customer? Because I can't imagine people not checking that :wtf:
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Sander Rossel wrote:
do you mean "release" as in a release to a customer? Because I can't imagine people not checking that
But you use Microsoft products! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
At one company we had automatic build that, originally, ran on all the dev environments each night. In our team we had a rule that if a build failed due to an untested checkin you bought treats - dog-nuts, cakes, etc - for those affected. One of my minions made a 'tiny tweak' to the build process itself. Next morning he came in to be confronted by 30+ failed builds... :laugh:
veni bibi saltavi
-
Shooting him is an act of mercy... I was in the line of skinning, boiling in oil... You know, the whole pack from the middle ages...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Kornfeld Eliyahu Peter wrote:
I was in the line of skinning, boiling in oil...
...then gibbeting on a lamppost outside the office, as a warning to others. :mad:
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
One arrogant prick I worked with did this. Checked in and got straight on Facebook. What a foster!
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Anyone who does this better have a real fast car.
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
This litte meme[^] is hanging on more than a few cubes where I work.
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave Kreskowiak -
At one company we had automatic build that, originally, ran on all the dev environments each night. In our team we had a rule that if a build failed due to an untested checkin you bought treats - dog-nuts, cakes, etc - for those affected. One of my minions made a 'tiny tweak' to the build process itself. Next morning he came in to be confronted by 30+ failed builds... :laugh:
veni bibi saltavi
Oops! :laugh: Was his face red after that?
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Surely, there's a MS joke in here somewhere.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
-
Oops! :laugh: Was his face red after that?
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
Yup and his wallet was emptied :)
veni bibi saltavi
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I refuse to answer on the grounds I may incriminate myself.
cheers Chris Maunder
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Well, honestly.. such people exist on the earth...
___@sHubHa
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
At one company we had automatic build that, originally, ran on all the dev environments each night. In our team we had a rule that if a build failed due to an untested checkin you bought treats - dog-nuts, cakes, etc - for those affected. One of my minions made a 'tiny tweak' to the build process itself. Next morning he came in to be confronted by 30+ failed builds... :laugh:
veni bibi saltavi
Our penalty was a round of beers on friday night. It had been known that 2am was not an unreasonable time to get home after a bad week. With 6 dev, 2 QC and a PM it was a bloody expensive round. It had been known to log on to a colleagues machine and insert a divide by zero if it looked like being a dry week.
Never underestimate the power of human stupidity RAH
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Pretty much all the time. It's the joys of PHP on a low volume website. If I break something, I've pretty much got 30 mins before anyone notices. For other languages, it the usual 'it works for me' scenario.
-
...know people who release code without checking it at all? :mad: (And do not tell you do it yourself!!!)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Release code me? NEVER! I have had team members who do this all the time. There Sh!t don't stink ya know. Never admits fault etc.... Check in code that doesn't compile. This I do alllllll the time. I leave a compile error where I was last working all the time. This helps me pick up where I left off in the code. Check in and commit code for even a dev rollout though. Nope don't do that. But then again perhaps I work differently than others. (who knew :))))
To err is human to really mess up you need a computer
