I've used 20 and 1 the absolute most, usually together. I've written quite a few programs, but I wouldn't consider myself a programmer (just something I have picked up on as necessity for using computers, because, face it, if you know how to use computers--you're expected to know programming to some degree by anyone who doesn't know how to use computers)."That's weird, it works for me.""Hmm...interesting...works on my machine."But this usually sparks me to go and review the code and figure out where it was happening. Also, I had written the lot of it using different versions of required libraries and so a bug usually wasn't found until I encountered someone using different versions. Depending on the project, I would either ask them to upgrade or modify the code to make it "backwards compatible".
Totally agree with blapierre - finding when the bug appeared should be simple enough - even if it was 250 builds ago, a binary search should find it within 10 tries or less. Then you could diff the code and maybe identify the offending change - unless you really plan to be a tester for the rest of your life.Nothing bothers me more than testers or coder/programmer/developers who say "I don't know how that works, it's somebody else's code." Of course it's harder to understand other people's code, but it all belongs to the company, and some day the guy who wrote it won't be here anymore - do you want all the code he wrote to become worthless when he leaves?If you're just in it for a paycheck, don't apply to my department - people like you can drain more value than you add.
meanfish, I'll acknowledge how lucky I am. I'm a programmer for a web-based CRM for auto dealers. It's the best job I ever had. I'm a lucky SOB!I thank God for the opportunity frequently.
I've been a developer, a QA geek, a systems support tech, etc. etc. (30 yrs IT experience) - so I've seen it all. If you're the QA geek, the worst thing to hear is:"I know it isn't perfect, but can't you let it pass? We need to get this into production!"(when NOTHING on it works AT ALL)...As in a certain infamous recent commercial, the answer is ALWAYS NO.
magamiakoNov 27, 2006
I've used 20 and 1 the absolute most, usually together. I've written quite a few programs, but I wouldn't consider myself a programmer (just something I have picked up on as necessity for using computers, because, face it, if you know how to use computers--you're expected to know programming to some degree by anyone who doesn't know how to use computers)."That's weird, it works for me.""Hmm...interesting...works on my machine."But this usually sparks me to go and review the code and figure out where it was happening. Also, I had written the lot of it using different versions of required libraries and so a bug usually wasn't found until I encountered someone using different versions. Depending on the project, I would either ask them to upgrade or modify the code to make it "backwards compatible".
yonasNov 27, 2006
Wow. Hilarious, sad, and true all at the same time. I use the hell out of #1 and #20. Guilty as charged!
anp14Nov 27, 2006
It works on my machine!!! Sooooo dead on...... man if I had a quarter for everytime a developer told me this, I'd be rich!
fastball1945Nov 27, 2006
I am not going to lie...I have used some of those before.
joemerchantNov 27, 2006
Totally agree with blapierre - finding when the bug appeared should be simple enough - even if it was 250 builds ago, a binary search should find it within 10 tries or less. Then you could diff the code and maybe identify the offending change - unless you really plan to be a tester for the rest of your life.Nothing bothers me more than testers or coder/programmer/developers who say "I don't know how that works, it's somebody else's code." Of course it's harder to understand other people's code, but it all belongs to the company, and some day the guy who wrote it won't be here anymore - do you want all the code he wrote to become worthless when he leaves?If you're just in it for a paycheck, don't apply to my department - people like you can drain more value than you add.
Closed AccountNov 28, 2006
LOL.... so true
cfchrisDec 2, 2006
meanfish, I'll acknowledge how lucky I am. I'm a programmer for a web-based CRM for auto dealers. It's the best job I ever had. I'm a lucky SOB!I thank God for the opportunity frequently.
bigkittyDec 11, 2006
I've been a developer, a QA geek, a systems support tech, etc. etc. (30 yrs IT experience) - so I've seen it all. If you're the QA geek, the worst thing to hear is:"I know it isn't perfect, but can't you let it pass? We need to get this into production!"(when NOTHING on it works AT ALL)...As in a certain infamous recent commercial, the answer is ALWAYS NO.
rezertSep 1, 2008
"That's not a bug! That's an unexpected feature!"
rezertSep 1, 2008
haha, agreed.
grindordieSep 3, 2008
You bastard!
kemadrumaJun 9, 2009
Lol, Its my favorite.