|
I was in a disaster recovery situation...
The PC that controlled a huge assembly line had gone dead (along with everything else in the building). There were 2 backups. Both were declared "dead" years ago. I am software, I don't support this thing at all, but my boss figured I could get anything to work, so off I go to the warehouse.
I ask the users what they do and how it works. They explain it to me and I listen. I realize the entire thing is controlled by a piece of software that wont start because of a missing pass code. As I poke around, I realize there is a batch file with the password in plain text, which starts the whole thing. I get it running after a grand total of 10 minutes. Everyone thought I was a hero. All I could think was, why on earth do they pay our tech services department? All 3 computers had the same problem... someone just needed to open the batch file, read the password, and type it into the program
|
|
|
|
|
Kind of sounds like some scenarios that I've seen, where only one person knows how something works, and they are conveniently out of the office.
"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
|
|
|
|
|
While at Silicon Graphics in the mid-80s...
Tel Aviv University (TAU) calls: We're having major problems with the systems. please come immediately, without delay!
Me: Well, lets do some troubleshoo...
TAU: No! We've troubleshot this for 4 days and we can not figure it out.
Me: OK, I'll be there by Monday (it's Friday).
TAU: No! Come now. Be here by tomorrow. Classes start Monday.
Me: OK, I'll be there as quick as possible, but that is an extra $15,000 in emergency assistance per the contract.
TAU: That's fine! Come now.
So, I literally got on a plane within 45 minutes (no TSA back then...), arriving the next day.
After 7 minutes "onsite", I discover someone switched off the powerstrip behind the desk.
Logged the call as "Emergency Electrical Flow Reset & Recovery", you know, so it looks more 'impressive' on the bill they'll soon get.
Me (a week later): Here's your $30k bill.
TAU (a month later): Well, we fired the $32k/year computer tech; we should recoup some of that.
|
|
|
|
|
Member 11683251 wrote: It's like people isn't even trying.
Nay, nay and thrice nay. It takes years of practice and sacrifice to get that useless!
|
|
|
|
|
On average, an American man will have sex two to three times a week; whereas a Japanese man will have sex only one or two times a year. ...This is upsetting news to me............ I had no idea I was Japanese.
New version: WinHeist Version 2.1.1 new web site.
I know the voices in my head are not real but damn they come up with some good ideas!
|
|
|
|
|
A university student generally has sex on the American schedule. Another person is involved on the Japanese schedule, if the student is lucky...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Those Vapor boys ... well, I feel sorry for them ... they didn't have the right kind of drugs growing up.
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
Mike Hankey wrote: On average, an American man will have sex two to three times a week;
Only because they include the gentlemens videos production
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Jeff Albertson said:
Inspired by the most logical race in the galaxy - the Vulcans - breeding will be permitted once every seven years.
For many of you, this will mean much less breeding. For me, much, much more.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Bloody hell, I aspire to become Japanese.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I aspire to aspire to being Japanese!
|
|
|
|
|
So you're not getting any at all!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I'm very suspicious of these studies: not one of them I've seen has a control group with their hands tied behind their backs.
cheers, Bill
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
That only happens in Tie-land.
|
|
|
|
|
Not the insecticide, but "Development Driven Testing", as opposed to TDD. It's what I've been doing for over a week now to please the people high up (or the client or whoever).
As you know, the usual practice is to write the test first and then do the implementation, but since no tests were written and the contract says we have to unit test the thing, I'm stuck with writing tests *after* everything is implemented. For other peoples code, written with no testing in mind. In C. ******g pointless waste of time.
--- edit ---
Self-censored to please the little dyslexic prude who reported this as abuse.
modified 28-Aug-15 22:44pm.
|
|
|
|
|
Guerrilla Coder wrote: pointless waste of time
Nah. It proves the tests work...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Guerrilla Coder wrote: pointless waste of time.
Until the code needs maintenance (or refactoring) - then you'll be glad you have "I didn't break something else" tests in place?
|
|
|
|
|
I meant it should have been done the other way round, that would have saved so much time.
|
|
|
|
|
You could always delete the code, write all the tests, then write new code to pass the tests..
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
And be responsible for everybody's bugs. Yes, I like that. I'm going to dedicate my weekend to that.
|
|
|
|
|
Guerrilla Coder wrote: and the contract says we have to unit test the thing,
That CDT - Contract Driven Testing.
Marc
|
|
|
|
|
When you see code in the project like
if (unitTesting)
{
...
}
else
{
...
}
it is officially time to jump ship.
|
|
|
|
|
Sometimes it is worse
#if defined UNIT_TEST
...
#else
...
#endif
|
|
|
|
|
I wish my colleagues were that smart.
|
|
|
|