|
|
And you didn't chose words to get him fired?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
He's not that kind of stupid, and I'm not that kind of evil.
|
|
|
|
|
[C# required]
Now you just create a "Excel Uploader" program that uses Excel Interop, and quietly make a CSV and uploads that instead.
I actually had to use a website that was too complicated for the end user, so I used a WebX and auto-filled everything it could detect. Unfortunately file open dialogs can't be filled in programatically, so I used SendKeys.Send() on a Timer for that.
|
|
|
|
|
Jörgen Andersson wrote: He's also good with buzzwords, One place I worked hired a VP of Technology who was nothing but a big bag of buzzwords. In the mid 90's he was strolling through our prairie dog village and telling us that Flash memory was going to replace the RAM in our desktops. This was the age of "paradigm" in every memo. He was a real "Management by Magazine Article" type guy. He proclaimed the company's mainframes dead and replaced them with minicomputers. One machine (long in the tooth) used Autocoder and all the programs were to be converted to COBOL. Once all the programs were converted to COBOL, it would be easy to maintain them, he claimed. My observation that a badly written program is hard to maintain in any language was ignored. The future was beckoning.
A throwaway line in the Manager's Edition (the summation in the margins) of a Smalltalk book claimed it could be used to model a company. He then wanted us to write a Smalltalk program as a whole company simulator so upper management could explore layoffs and reorganization on the operation of the company.
Thankfully he was shown the door, but only after he miss-estimated how long the mainframe to minicomputer conversion was going to take and it cost the company an extra $10 million dollars in operational expenses.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
My best friend for >20 years still calls his tower the hard drive, and asks me how much 'hard memory' he has.
I still have no idea what the hell he thinks he means. He won't stop saying it. It means something between drive space and RAM in his head.
I've tried the "desk top / desk drawer" analogy. I've tried ripping it apart and showing him the actual components.
Nothing works.
He also runs a defrag when he thinks he sees evidence of malware, despite my assurances that he's waving a dead chicken at the thing.
Technology hates him. I've never seen anyone have so many problems from normal judicious use of a computer or smartphone. It's impressive.
|
|
|
|
|
mikepwilson wrote: Technology hates him. I've never seen anyone have so many problems from normal judicious use of a computer or smartphone. It's impressive.
So You haven't met MY Brothers. One asked me to fix his email. What happened is he forgot his password.
David
|
|
|
|
|
He called me on my way in to work this morning. One of those "fake anti-virus" trojans.
"But I didn't DO anything."
"The fact that it's there proves that's not true."
He wasn't pleased. But dammit! Stop clicking on s***!
|
|
|
|
|
mikepwilson wrote: My best friend for >20 years still calls his tower the hard drive,
I find that to be quite common for people of my parents ages and older (60's plus).
|
|
|
|
|
Some one I know calls the whole computer (tower and all) the CPU - it drives me nuts (possibly why he still does it!)
|
|
|
|
|
At least that's closer.
I'm convinced there's a subset of civilians who absolutely adore doing this kind of thing to us.
Like the XKCD comic about sending typography geeks cards in papyrus.
|
|
|
|
|
|
From tech people (unfortunately): A while ago our company started using Entity Framework and databinding. Completely unrelated I created a library we could use for a certain type of software. Appearently some people thought the one couldn't do without the other. So I got questions like "We can't use EF for this, should we use your library?" or "I need something else than EF, because I can't bind this value" and I'm just sitting there like "What does that have to do with anything?"
Luckily things have been better lately.
|
|
|
|
|
My brother usually has these problems:
- Microsoft is not working (he means Word)
- Mozzarella is not working (that is Firefox, apparently the cheese name is easier to remember than the actual company name)
Make it simple, as simple as possible, but not simpler.
|
|
|
|
|
A fiend refers to the computer (everything apart from mouse, keyboard & screen) as the "hard drive".
|
|
|
|
|
Member 10685535 wrote: A fiend refers to the computer Was he a fiendish fiend? Or just a run of the mill fiend?
Sorry, I couldn't help myself.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
The best I ever heard was somebody (who from the tone of their voice, clearly knew it all) referring to the manufacturer "Hewlett Packard Bell"
|
|
|
|
|
My mobile phone carrier's 3G speed is 500 MB
Yeah... How easy it is to sell to a layman?
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
----
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
My mother was worried upon receiving a new monitor that all of her data would be gone.
|
|
|
|
|
This topic reminded me of an occurrence in 1968 during the punched card era.
We had a "database" of around 50,000 punched cards for our inventory. Each card was a type of inventory item. Punched into a card was the identifying information, quantity on hand, price, etc. The punched cards were stored in 25 trays. 2,000 cards per tray.
They were kept in the user area where they could peruse them during the work day and brought to the data center at night to process all the orders and receipts to create updated punched cards which were merged into the deck replacing the out dated versions of each card.
One morning, the inventory department manager came down to the data center and told us that there we 22 cards missing from the deck. (That's 22 out of ~50,000) I still don't know how he determine that.
Anyway, he wanted us to run the ~50,000 cards through the computer and print out the missing cards.
|
|
|
|
|
User: It doesn't work!
Me: What doesn't work?
User: The button!
Me: Which button what happens when you click it?
User: The button on the page! Nothing happens I just get an error!
Me: What does the error say? tell you to do?
Then total radio silence on the subject.
|
|
|
|
|
Sad, but true, I used to work at a company that employed a full time QA department to test our code.
The most common explanation that accompanied bug reports were "I was doing something when it crashed."
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Boy, you have a well trained QA department! They know they have to write a bug report...
I've had the opposite problem at times. For instance, I was trying to write an automated test for a "back" button. Worked perfectly the first time. Asked to start, asked to "back" and it executed the back button. Run it again and the back button fails to execute because it doesn't exist. What's going on is that the button to go forward executed SQL commands, the data wasn't cached so it took a couple of seconds to retrieve the data. Next run, the data was cached and it moved forward to the next screen as designed and the back button didn't exist.
Now, do I write a bug against the code because it works as designed causing my automated test to fail or against my automated test because it can't consistently test the back button.
|
|
|
|
|
KP Lee wrote: Boy, you have a well trained QA department! Yes, yes, we did.
It was interesting place to work at for all the wrong reasons. We had one old gentleman who was disgruntled that his ideas for the code design was being ignored, so he used to write up bug reports so the resolution would be to implement his design without the usual review. We finally caught on.
We didn't use automated testing, instead we had to write scripts explaining point by point what to enter and click, along with the expected response, assuming no prior knowledge of the application. The QA department liked to hire kids from the high school across the street to do regression testing.
It didn't help that we also had clueless designers. Our coding team was pretty good, but we had to deal with non-technical designers and incompetent management. The designers didn't want to see cursors (this was back in the day of text screens) blinking, so the previous set of programmers had been instructed to hide the cursor off screen...and then wondered why error messages were not being displayed. To solve that, they took to logging errors to the hard drive...including "out of disk space"
But the one bright spot was when they did decide to tackle the error message displays to make them unambiguous. Since there are errors that can occur in different places for the same reason, some had taken to using different wording to indicate to the programmer where the error had occurred. In the same vein as "You are in a twisty maze" versus "The maze is all twisty." Subtle differences lost on the QA department. We wanted numbers, but the non-technical designers deemed them "too technical", but we finally agreed on a compromise of a number followed by a message. Radical eh? Our hope was that we could get people to at least write down the number. A forlorn hope.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Another radical idea, set up a DB that tracks the error message and the program file that creates the message and when it is inserted into a table maybe the line number in the file when it was recorded (At least the function it is in) and you then use the identity field's value in the error message.
When you look up the records that match LIKE '%maze%' you can then list all the messages and ask them to identify which one they got, so they can say "I dunno, doe-N rememer"
|
|
|
|