IT Quotes I Like
-
@scottalanmiller said in IT Quotes I Like:
@dafyre said in IT Quotes I Like:
@travisdh1 said in IT Quotes I Like:
@hobbit666 said in IT Quotes I Like:
PICNIC
Problem in Chair NOT in computer
I just did a quick search of this thread, and we're missing the other classic!
PEBCAK
Problem Exists Between Chair and Keyboard
See Also: PEBKAC -- Problem Exists between Keyboard and Chair
Otherwise it is pronounced with an "S" sound.
The letter "c" followed by the letters "a", "o", or "u" is typically pronounced as a "hard" c (sounds like "k") such as in the word car, Carolina, curve, course...etc. To make the "c" sound like an "s" when it is followed by the letters "a", "o", or "u", you would typically need a cedilla under the "c". Rare exceptions to this are the common "facade" which was derived from the French word "façade" where the cedilla was eventually removed and pronunciation unchanged.
As with other English rules, this is generally the rule that applies most often, and since this isn't a typical word (acronym really), I believe the general rules would apply. So you could use PEBCAK
-
IT Job is no thanks Job....
-
Added:
Strict hierarchy is a socially acceptable way of stating "intentionally suppressing exposure".
-
"Sufficiently advanced incompetence is indistinguishable from malice."
Granted this covers more than just IT, but so very relevant.
-
@travisdh1 said in IT Quotes I Like:
"Sufficiently advanced incompetence is indistinguishable from malice."
Granted this covers more than just IT, but so very relevant.
Who said that? Sounds like something I would say.
-
@scottalanmiller said in IT Quotes I Like:
@travisdh1 said in IT Quotes I Like:
"Sufficiently advanced incompetence is indistinguishable from malice."
Granted this covers more than just IT, but so very relevant.
Who said that? Sounds like something I would say.
It was posted somewhere in the last week
-
@dashrender said in IT Quotes I Like:
@scottalanmiller said in IT Quotes I Like:
@travisdh1 said in IT Quotes I Like:
"Sufficiently advanced incompetence is indistinguishable from malice."
Granted this covers more than just IT, but so very relevant.
Who said that? Sounds like something I would say.
It was posted somewhere in the last week
I got it from Steve Gibson, but he was quoting someone else, and I wasn't fast enough to write down who he got it from.
I agree, sounds very much like something you'd say @scottalanmiller.
-
This is one I hate more than anything:
"That's not how we do it, because we've always done it this (other) way"
Okay while why? What issues have happened, what reasoning is there?
-
Raises are given when the company is healthy, titles are given when things are going badly.
-
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
-
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
-
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
-
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Depends on the contract.
-
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
Hours bid generally means that those hours are negotiated and the expectation is that finishing faster does not mean lower cost.
-
@scottalanmiller said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
Hours bid generally means that those hours are negotiated and the expectation is that finishing faster does not mean lower cost.
Yeah it depends, but that's now how it seems he meant it. I took it as the customer paid for hours worked, not hours negotiated up front.
-
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
You fix this by bidding the project, not the hours. Of course, this can royally bite you in the ass.
-
@scottalanmiller said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
Hours bid generally means that those hours are negotiated and the expectation is that finishing faster does not mean lower cost.
It seems odd to use an hour marker in this situation, instead of just a bid dollar amount, but whatev'
-
@dashrender said in IT Quotes I Like:
@scottalanmiller said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
Hours bid generally means that those hours are negotiated and the expectation is that finishing faster does not mean lower cost.
It seems odd to use an hour marker in this situation, instead of just a bid dollar amount, but whatev'
Because... customers.
-
@dashrender said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
You fix this by bidding the project, not the hours. Of course, this can royally bite you in the ass.
It's more that you bid for a minimum.
-
@tim_g said in IT Quotes I Like:
@scottalanmiller said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
@tim_g said in IT Quotes I Like:
@wls-itguy said in IT Quotes I Like:
Had a boss when I was at my first IT job say "efficiency doesn't always pay the bills"
We were arguing over the fact that we estimated a job to be 25 hours and it only took us 19. Rather than sit at the job for another 5 hours to make the money we wrapped up. The powers that be didn't like that. I wasn't there too much longer
That could be considered stealing imo.
Happened all the time. Bid X # of hours. Finish early, drag it out until we hit the hours bid.
Hours bid generally means that those hours are negotiated and the expectation is that finishing faster does not mean lower cost.
Yeah it depends, but that's now how it seems he meant it. I took it as the customer paid for hours worked, not hours negotiated up front.
Coming from the software dev side... I only agree with that in cases where you have total confidence that overruns would not meet with resistance. I know that that is kind of impossible to predict, but you know how it goes. If it is truly hours, there is little need for the estimate. What if the time went over by 50% or more? Would the customer have pushed back? If so, there is little or no justification for accepting fewer hours either.
In one time transactions, this is a tough situation. But I can tell you, software shops get burned by this. They have to take profit where they can get it, because there is so much refusal to pay if the estimate is off in the other direction.
