Well:
1. Tracking hours for a developer is just plain silly. You can't properly quantify hours of work in any meaningful way. It's at least as arbitrary, and somewhat random, as a salary. Except it makes it easier for a developer who is unscrupulous to rip you off. Especially in my situation, where you don't have people familiar with the software development cycle monitoring what is happening.
2. If you must have a developer track his hours, at least do it electronically with some kind of web page that stores the information. A smart developer will probably also track the hours in a separate worksheet if s/he suspects the company might shave hours off unscrupulously. But then, a smart developer would leave such a company and find a better one in which to work.
3. Ripping off a developer is a very bad business decision. Very bad. Astonishingly bad. A bit like chopping-your-own-head-off bad. And probably unnecessary, as some developers will work under ridiculous situations if you're just nice to them.
Anyway, I filled out my timesheet manually. I'm going to do anothe rone of my daily 'so where are we with my electronic timesheet filing problems today' forays into corporate hell a little later today.
well, its as fine grained required that I did this once a month ;-)
nowadays with the webif usually once a week...
Point is that some places like hours accounted for.
Enough places like it that there are good, easy-to-use solutions out there.
Klok is one.
Toggl is another. (I like Toggl better)
If your company is using something that isn't comfortable, it means they suck.
I can't speak to the security concerns for those particular solutions, but this company is extremely concerned about security, given its nature. That drives their decisions to no small degree, I expect.
Anyway, I filled out my timesheet manually. I'm going to do anothe
Just remember, we're using the new cover sheets on the TPS reports now.
Seriously.
"Yes, we are still working on it. I apologize for the delay."
Hehheh... but, y'see, I have worked in the military, and I know that to get anything done, you have to pester people. He can expect me to e-mail him again tomorrow. And again. Until it is resolved.
Well, I'm on Planview.
I wonder if I'll get paid. My respective companies are having to hash out logistics now.
I hope I don't have to deal with multiple timesheets.
If I wasn't caught up in the middle of this, I'd find it all strangely hilarious. Q: Why did our one client "win", and get everything they want, while others have to wait? A: because sales promised it, and then they said "Ok, deliver. Nee."
We didn't expect them to say "Nee." So they win.
We didn't expect them to say "Nee." So they win.
There's this guy at the office who has a fascinating walk.
I guess he works out, 'cause he carries his arms out like a person who works out. But then he has this funny little pep in his step, almost as if he were that Crumb image of the Keep On Truckin' comic. Or maybe he was in a Mickey Mouse episode walking down the road while some old piece of music was playing.
When they ask for their SECOND shrubbery, I think maybe we get to just
ignore them.
All shrubberies have been outsourced to a Chinese company for manufacturing.
Sorry, you lose your shrubbery coordination job. Also they hire illegal immigrants to deploy the shrubberies back into the US at below minimum wage (but you get to pay for their health care).
They are the Knights Who Say "Jobs" -- they're from the government and they're here to help you.
I just realized this company has TPS reports.
Seriously.
They're generated by some mail server thing that notices spam in your mailbox and generates a report to let you know you can have the system deliver the spam or get rid of it... but they still have TPS reports.
They are not, however, given to us with cover sheet.