Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
A case of "You show me how I'll be measured, and I'll show you how I'll behave".
At one site, the helpdesk performance was measured on how quickly priority 3 calls were addressed. The first thing we did was try to get the calls upgraded to priority 2, or downgraded to priority 4.
At clientco they have similar systems and I heap similar abuse on them. Most teeams dont do this - and get marked down. They concentrate on getting the job done and helping people!
A case of "You show me how I'll be measured, and I'll show you how I'll behave".
At one site, the helpdesk performance was measured on how quickly priority 3 calls were addressed. The first thing we did was try to get the calls upgraded to priority 2, or downgraded to priority 4.
Exactly how the police, the NHS, the railways, etc, approach their HMG targets.
A case of "You show me how I'll be measured, and I'll show you how I'll behave".
At one site, the helpdesk performance was measured on how quickly priority 3 calls were addressed. The first thing we did was try to get the calls upgraded to priority 2, or downgraded to priority 4.
LOC has been used as a metric by idiotic managers. I don't think anybody is stupid enough to do that anymore, but I wouldn't be too surprised.
Big US investment bank I was working for there brought it in last year. They claimed that it was just for research but there would be emails asking you to justify your output if it was not the same as the previous month. They said that it was to count the lines modified or added before and after a release but they factored in the teams cost to give a cost for line of code added. Everyone ended up writing code to frig the results.
LOC has been used as a metric by idiotic managers. I don't think anybody is stupid enough to do that anymore, but I wouldn't be too surprised.
I knew one team whose manager had decided that he could measure their performance by the number of bugs fixed per month. Towards the end of the month, they would enter a load of bug reports describing various manifestations of a single bug for which they had a fix. Then they'd mark all those bugs as duplicates of the original bug, fix that, and hey presto! two dozen bugs showed up as "Fixed" on the monthly report
REminds me of a story I heard from Digital - coder fixed a bug and introduced 4 other bugs while doing it - patched them all. Then got pulled into Manager's office and congratulated for solving 5 bugs in 1 day!
I am sure in Japan in late eighties that coders wwre paid by line of code? Or did I imagine it?
LOC has been used as a metric by idiotic managers. I don't think anybody is stupid enough to do that anymore, but I wouldn't be too surprised.
I knew one team whose manager had decided that he could measure their performance by the number of bugs fixed per month. Towards the end of the month, they would enter a load of bug reports describing various manifestations of a single bug for which they had a fix. Then they'd mark all those bugs as duplicates of the original bug, fix that, and hey presto! two dozen bugs showed up as "Fixed" on the monthly report
You cannot polish tulip as they say. I have to admit I have not seen a well written bit of software for years. Some of the stuff I see is so bad i'm surprised the writers can actually get it to compile.
Is there any point in writing good code? Nobody else does it, why should I.
Broken window syndrome in action.
New developments, I write good code. When maintaining code that's well written, I write good code. After all, the next person along to maintain it may be me again.
When maintaining code that's badly written, I really can't be to make the effort.
In my BillG review meeting, the whole reporting hierarchy was there, along with their cousins, sisters, and aunts, and a person who came along from my team whose whole job during the meeting was to keep an accurate count of how many times Bill said the F word. The lower the f***-count, the better.
Leave a comment: