|
Are you tired of Ursa Minor Beta?
|
|
|
|
|
And when the clocks go back? That takes you over 24hours for that day!
|
|
|
|
|
I remember one job the time sheet system complained at anything over 20 hours. Regularly broke it and we had to get a fix to permit 100+ hours in a week.
|
|
|
|
|
I'm in the same boat. However, the OP looks to be under contract and not a salaried employee (maybe I'm wrong), he's getting paid for each hour worked, who cares what the other people are doing?
"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
|
|
|
|
|
Quite.
I read is as he's brilliant, and everyone else is sh*t, which is why he gets paid the big bucks as a contractor, but because the sh*t salaried people work longer hours than he is prepared to it makes his sticking rigidly to the clock and going home look bad.
He isn't bad, he's good, he's better in fact.
It's so unfair.
Beats fists on floor, threatens to hold breath until passes out, and so on.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
meeee-kin-owww!
Put your claws back before you rip your handbag!
|
|
|
|
|
You can't worry about what you have no control over.
chriselst wrote: threatens to hold breath until passes out Oh goody!
"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
|
|
|
|
|
Well...I *am* pretty awesome, but that's beside the point; thank you very much for noticing.
The larger point is that expectations of estimates get created based upon unrealistic results. Billing an 8 hour day but spending "14" hours on those tasks pollutes any project plan and makes honest assessments of the effort necessary to complete work look "slow." Then you lose more time trying to explain to people why things won't just be done when they come in the next morning as if by magic.
Past behavior sets future expectations and "your" lies end up directly impacting my ability to sell an honest product.
"I need build Skynet. Plz send code"
|
|
|
|
|
Re-read the OP's post. You completely missed the point.
When management sees an estimated 1,000 hour project complete "on time" they estimate all future projects with that project as the scale. If the project actually took 1,500 hours to complete? Guess what, the next one will, too.
The worst thing is the people who KNOW this is true, but estimate that same project at 1,000 hours anyway as it's what management/clients expect.
|
|
|
|
|
I didn't miss the point, I was making a joke, although some people don't understand what they are reading is a joke unless it has a joke icon.
Although his point wasn't quit your interpretation in my opinion.
Someone else nailed it when they talked about the phrase billable hours. Absolutely the management need to know who long something really took, but just because those on a salary stop all night to get something working doesn't mean that they were not recording their time against the project, I'd be very surprised if they were not.
Even more important they they understand what those hours were spent on. Did the initial dev take longer than expected, did it come back from testing with a load of extra work needing doing. Where the devs not good enough, the spec not good enough, the requirements gathering not good enough.
Maybe it really should have taken 1,000 hours, but took 1,500 because something went badly wrong.
Surely better to fix what went wrong and do the next one in 1,000 hours than just keep the crap and stretch it out to 1,500 instead.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
jeron1 wrote: I have to ask, what do you care what the salaried employees do?
The real problem of course is that it means that the professionals don't understand the impact of that on the business. There are probably many but some include
- There is an expectation that everyone should work those hours
- Some employees don't want to work that long but do because of the expectations.
- Some employees cant work that long but feel like they are not contributing.
- Some employees that work that long, like doing so, but resent the ones that don' also do it.
- The above two impact moral in various ways. And moral is something that has been proven to impact productivity.
- When a normal work week consumes all the time that employees have then when an emergency develops something will fail because there are no hours left.
- Often such extra work is never added into the project thus there is no way a business can create an accurate project plan.
- The loss of a employee can hurt a normal project but, because employees have extra time, they can make up for that. Obviously when there is no extra time no one can make up for it.
- Over work very likely means cutting corners, which can impact quality. Doesn't of course mean that it it crap but it is unlikely that it as good as it could have been.
|
|
|
|
|
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
This girl I used to work with was complaining once about all the extra time we were putting in to get a job out the door...she said, 'All this extra time we're putting in reduces my hourly pay to "do you want fries with that?"'
...made me laugh...
|
|
|
|
|
This may not be a valid comparison if McDonald's employees get their way...
|
|
|
|
|
Very true but then they're going to be replaced by vending machines and robots...McDonalds will become a cafeteria.
More programming work for us...
'Woops, sorry!...the code threw an unhandled exception and injected special sauce into the cherry pie!'
|
|
|
|
|
"special sauce"
|
|
|
|
|
I thought it was apple pie[^]
"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
|
|
|
|
|
When I came to that same conclusion at a job, I found another job.
|
|
|
|
|
I've been freelancing for 20 years now...if I'm working overtime because of something I did wrong, I don't charge them for it...if it's because of something they did wrong or just underestimated, no mercy
The girl in question didn't really have that much to complain about...a couple of overtime nights maybe 4 times a year...I've worked 36 hour shifts to deliver on ridiculous deadlines...have the nervous tick to prove it
|
|
|
|
|
I understand. My situation was as a salaried employee who worked 7 days a week, 12+ hours a day, for two months straight. It stopped at 2 months because I took a previously scheduled vacation. When I returned it was more of the same with a few weekends off.
|
|
|
|
|
Yeah, I'm not unsympathetic...they do go way overboard sometimes asking people to put in 'extra'...those places are rightly called 'sweat shops'.
|
|
|
|
|
I agree, but the bigger issue is that working "unbilled" hours will often adversely affect estimates for future projects. The project manager must know the actual time spent for the current project. Remember that "extra" hours spent on the current project are probably due to a bad estimate based upon what was understood from the previous project.
While no estimate will ever be accurate, at least start with good data.
|
|
|
|
|
Sorry, but if the dev is crazy enough to accept more work without moving the planning, then he/she should be bitten by it.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
But the whole team can be bitten.
|
|
|
|
|
What's wrong here is the entire premise of hourly pay.
If you are a contractor and you are charging me for every hour you work - then I want you to be working for every hour you bill. Not having a break, stretching your legs, writing a shopping list or getting on Farcebook.
with a company charging a customer for a job of work, the customer isn't paying for a number of hours - they are paying for a product - and if people need to work longer hours to get the product out the door, then that's a good thing; a happy customer is a good customer.
of course, this shouldn't become a constant requirement of the employer - the next project, folk should be able to chill a little, safe in the knowledge that they have learned from the bad experience, and adjusted their estimates accordingly.
Alaric_ wrote: "heroic effort" to making their screw ups not look like screw ups
so are you saying that, when you screw up, you charge the customer for the time it takes you to fix it?
So, if a plumber comes to fix a washer on your tap, then breaks a pipe and takes all day to fix it, do you just grab your cheque book and hand over a day's work for a 1/2 hour job?
PooperPig - Coming Soon
|
|
|
|