The continuing hell of continuous meetings
-
In this case I'd add the time range to the drop down, or display it somehwere. UNless that's prohibited, too :)
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchyThat was my first thought. Or if they choose a time have two boxes then fill in with the soonest time and another with the latest time. I also agree that while it sounds redundant you need to attempt to code for stupid once in awhile :-D
------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
-
Hi Rob, Well, on behalf of Camels everywhere, let me add that Bactrian camels, packed with 85kg. loads (187 pounds), over a thousand years ago, on the "Silk Route," could go for three days without water as they crossed the totally arid Taklamakhan desert (of course the caravansarais travelled by night). If a committee designed the Bactrian Camel, I'd buy their software. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
BillWoodruff wrote:
If a committee designed the Bactrian Camel, I'd buy their software.
If the committee that designed the Bactrian Camel designed software, the app would take an hour too boot, have buttons larger than the forms they sit on, balk at commands, stink to high heaven and frequently spit. In short, you would have one of the newer versions of MS-Word.
-
ChrisElston wrote:
The greatest problem with software design is trying to catch all the stupid things users can do.
Tell me, we write the software the way we expect it to work. We never diviate off the path. Once a user gets their hands on the software, well that's when the bugs being to manifest the software.
Software Kinetics - The home of good software
Really too true ...
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. Well - just try to be in the situation of the WOman in the help desk; they should concentrate about the customer, and not on (even simple) math .. . And better than a sheet would be some additional field in the app that tell the user the times before and after, so he could read them right from the screen
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
Sounds like a typical week for me...I refuse to bring paper and pencil to any meeting as it’s just a flat waste of my time. The users here change their minds so often it might take 20 revisions to get them something they will stop whining about. X|
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
-
peterchen wrote:
A crib sheet is a silly kludge, a reaosnable design would use start and end time. Giving a time to a customer and appearing half an hour earlier is asking for trouble. Or... interesting experiences, at least.
It is actually the result of a regulatory requirement. The company this is for being very heavily regulated by the government in terms of practice and especially making payments to customers for doing something wrong - which is what this relates to.
Every man can tell how many goats or sheep he possesses, but not how many friends.
I'm in the same situation meeting wise. . . but I do have a suggestion for your crib sheet issue. Why not have the system display the time 1/2 hour either side of the selected time. The user selects 13:15 and the screen displays "you will be called between 12:45pm and 01:45pm" (mixing 12 and 24 hour clocks as another form of idiot safeguard) - then the user can just recite what's on screen to the caller.
-
Sounds like a typical week for me...I refuse to bring paper and pencil to any meeting as it’s just a flat waste of my time. The users here change their minds so often it might take 20 revisions to get them something they will stop whining about. X|
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
I had a great one like that recently. Spec: the IsPrepayment field should take a constant value of 'Yes' Me: Done Analysts: We got an error when uploading. The IsPrepayment field should be blank. Me: No worries, I'll change the default to blank - though that's different to the spec; are you sure you want me to go ahead? Analysts: Yes, set IsPrepayment to blank. Me: Done Analysts: We got an error when uploading. The IsPrepayment field is blank. Did you deploy the change? Me: Yes - as the error points out, the prepayment field is now blank, which is what you asked for (see mail thread). Analysts: Please can you set it to "No"? Me: But it is a prepayment, and originally the spec said it should be Yes, which made sense. Are you sure you want it to be set to No, that seems illogical and will cause confusion to anyone trying to support this. Analysts: Yes, it's OK, the system doesn't actually use that field, we just need to provide it to get the upload to work. Me: In that case, should we remove that field from both systems - there's no point sending something which isn't being used (and also no point having validation on it if we keep it). Analysts: We may need it in future; please default to 'No'. Me: Done (sigh) Analysts: it works!
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
"Each time I gave the exact answer, word for word." I love that. You are the most loved guy in that company? I also hate those meetings. We also have calls where all - i really mean all - people have to attend. From supporters over testers to development, business analysts, really everyone. Only to say some things and show boring powerpoints that just waste time. There's always an alternative to send around the same information in much less time. This is when I think, if they really make themselves clear how much money goes down the drain when all people sitting there just waiting for the end.
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
True. I could have found a canal too, but I prefer to scream in my fist and pretend I have cramps. It is astounding to me and even after almost 7 years spent in Canada I still get surprised by the sheer amount of people that don't deserve their salaries. I ask myself every day, how is this country a developed country when almost at every corner I meet people that reached a long time ago their level of incompetence. The horror of meaningless meetings where people are repeating again and again the same things because they don't know sh..t but they have to give the appearance of participating. Who is keeping the bar raised where it needs to be so things don't crumble? I guess that as always, out of each 100 people employed probably only 25% are really doing the job and doing it properly. Sometimes I imagine how life would be on an alternative path, like when I would have the guts to stand up, slap them and let them know how I feel. It helps for a few seconds but then back to reality. What to do? Cheers.
giuchici
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
ChrisElston wrote:
I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?".
"Yes" came the resounding reply.
So, it's not really the seemingly endless meetings, but the stupidity with which you're forced to deal that is driving you up the wall. Allow me to be part of the choir to which you preach. I hope today's better for you.
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
-
I remember reading of a meeting with the sign on the door saying These Meetings Will Continue Until We Discover Why No Work Is Getting Done! Maybe you need to bring one of these http://www.bringtim.com/[^]
Psychosis at 10 Film at 11
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
I feel better - we're down to one department meeting a month - cancelled when the manager is out of the office, and one team meeting a week (currently on two teams). I've had other jobs with endless meetings - four-plus hours at a shot, and that was solved with a new boss who gave each manager one powerpoint slide and 3 minutes. If you couldn't get it done inside those limits, "you weren't doing enough staff work", and "Staff work isn't done at Staff Meetings" and "Staff Meetings are for me, not you" were his mantras. Morale shot through the roof after the first meeting! On the other topic: I'd recommend changing the drop down to reflect the hour that they might get a call (and need to be available) When may we call on you?* >0815-0915 >0830-0930 >0845-0945 *You may expect to be contacted during the hour you select. Calls typically take up to 30 minutes to complete. Perhaps you can schedule a meeting to discuss...?
-Bob
-
ChrisElston wrote:
I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?".
"Yes" came the resounding reply.
So, it's not really the seemingly endless meetings, but the stupidity with which you're forced to deal that is driving you up the wall. Allow me to be part of the choir to which you preach. I hope today's better for you.
Occasionally don't go to meetings, test the water and eventually you'll reduce your meeting load. I try to follow some guidelines like these... http://pmtoolsthatwork.com/boycotting-meetings-as-a-project-management-tool/[^] Also, lack of communication I find is a major issue in many companies. Many meetings don't often constitute as communication though, as people don't speak up, they sit quietly biting their tongue. I would liven up meetings by really blowing some wind on concerns you have, putting people on the spot and make the meetings more exciting: in the long run it will be beneficial for the team, department and company. Often, many people percieve the project from their own little world. As Piaget noted in children's learning; a child (or person with the mental ability of a child as you mention having many in your meetings) creates a mental model of the world (or of an IT project) that can be flawed and through cognitive constructivism this model can be challenged and reformed by other children in the classroom (or by other employees in a meeting, in your case). So, maybe they understand more your concerns and you understand more of why they are making decisions that you don't understand. So speak up, and if the meeting goes down the route of being a waste of time, I would speak up about that. However, this approach can be of high risk, and you need to be careful not to 'annoy' people who if challenged will be aggresive. Personally, I get much more upset if I am biting my tongue, and this is my motivation for speaking out in meetings, although I do so less if I am not too familiar with the people in the meeting.
-
BillWoodruff wrote:
If a committee designed the Bactrian Camel, I'd buy their software.
If the committee that designed the Bactrian Camel designed software, the app would take an hour too boot, have buttons larger than the forms they sit on, balk at commands, stink to high heaven and frequently spit. In short, you would have one of the newer versions of MS-Word.
Gregory.Gadow wrote:
BillWoodruff wrote:
If a committee designed the Bactrian Camel, I'd buy their software.
If the committee that designed the Bactrian Camel designed software, the app would take an hour too boot, have buttons larger than the forms they sit on, balk at commands, stink to high heaven and frequently spit.
In short, you would have one of the newer versions of MS-Word.
Can I vote twice? this deserves higher then a 5.
///////////////// Groucho Marx Those are my principles, if you don't like them… I have others.
-
:thumbsup: I like it, I like it a lot. Must be an app for it somewhere.
Every man can tell how many goats or sheep he possesses, but not how many friends.
Ha! There is an app for that! A team lead asked me to write a quick "stay on top" clock a few years ago - it sits in the bottom right corner of the screen during management team meetings. You input the number of attendees and the average hourly rate and click go... adds up quick. The other managers thought it was funny, but stopped smiling when told it was doing "real math". http://www.katein-taylor.com/whatsitcost.png[^]
-Bob
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
If you have somebody telling you your customers are that stupid, better listen. That meeting turned out to have value. There have been suggestions before about how to deal with this, but you will probably end up doing way more. You may have to have a "greeter" call the customers, and only switch them to an actual person if they answer the phone, or some such adaptation. Users are what they are. You can't change it. You have to adapt or die. Don't sit in a meeting and program. This is so disrespectful. It just encourages stupid meetings by saying, "I'm not paying attention anyway." You can choose not to attend meetings that are not well-run. If the meetings don't produce an agenda and minutes, you cannot be held responsible for ignoring decisions made at those meetings. Simply deny remembering the decisions were ever settled. If they insist, ask to see the minutes. (But do read meeting minutes). You can leave meetings if they haven't wrapped up at the scheduled end-time, saying, "You only scheduled 1 hour, and I have another meeting." If your company has a lot of meetings, how can they not believe you? If stakeholders don't show up, you can leave after a couple minutes, saying, "Call me if Bob shows up." Don't wait very long. This behavior might catch on, causing meetings to start on time. Efficient meetings show respect for the participants. If you run meetings, you can produce an agenda in advance, demand concrete action items before wrapping up, end on time, and produce minutes. You can immediately terminate and reschedule the meeting if important stakeholders don't show up, and note their absense in the minutes. You may find that if people can see what an efficiently run, effective meeting looks like, they will want to have one too. It is possible for one person to change the culture of a whole workplace. If you skip stupid meetings in favor of adding value by writing good code, you will become bulletproof, because you will be more productive than your colleagues who waste their time in meetings. And if this doesn't work; if they demand you attend hours of poorly held meetings, well, you get paid the same hourly wage for attending a stupid meeting as for writing brilliant code. Don't work overtime. Tell your manager, "We had 20 hours of meetings this week. If you expect us to be productive, you *must* cut down on the meetings." And if they let you go for not attending badly run meetings, it's as if they'd given you a seat on the last lifeboat on the Titanic. Such a company is wobbling ba
-
I seem to be spending all my time in meetings these days, two Monday, two Tuesday, just a quickie yesterday, and three hours of hell this morning. Some of you may remember this[^]. I now yearn for meetings like that. There were nearly 20 people in this meeting, apart from myself and another technical woman who was leading the demonstration of some new software, and the bloke in charge of the project, the rest were supervisors and managers of the end users of the system, all but two were female. The levels of stupidity were astounding. Part of the system requires that an hour time slot is given to a customer on the phone by a user selecting a time from a drop down of 15 minute intervals (8.00, 8.15, 8.30, etc). It needs to be made clear to the customer that the time given means an agent will call at their house for up to half an hour either side of that time. Someone said "we will need to create a crib sheet for the users with each time they can choose and the corresponding time half an hour before and after it". I tried to let it go, it was nothing to do with me. "Do they really need a sheet to tell them what half an hour after 8.15 is?". "Yes" came the resounding reply. "But. But. That's called 'telling the time'. They cannot do that themselves they shouldn't have a job, they should be at school with my 5 year old. So she can explain how time works to them." Another woman asked a question that was totally out of scope of not only the meeting, but also the system we were talking about. I replied that we had a meeting scheduled next week for that. She asked the same damn question 4 more times. Each time I gave the exact answer, word for word. And on and on and on it went. I've been outside to scream at the canal.
Every man can tell how many goats or sheep he possesses, but not how many friends.
-
BillWoodruff wrote:
If a committee designed the Bactrian Camel, I'd buy their software.
If the committee that designed the Bactrian Camel designed software, the app would take an hour too boot, have buttons larger than the forms they sit on, balk at commands, stink to high heaven and frequently spit. In short, you would have one of the newer versions of MS-Word.
Gregory.Gadow wrote:
If the committee that designed the Bactrian Camel designed software, the app would take an hour too boot, have buttons larger than the forms they sit on, balk at commands, stink to high heaven and frequently spit.
:) Reminds me of earlier versions of Windows' OS, like XP, and IE6, except: they could not carry their loads, and dropped dead frequently. And ... to extend the analogy ... was developing using COM not like crossing the Taklamakhan ? best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
