Ho! I should add that with a strategy like that, no body would want to
work on bugs because their "apparent code production" would go down
big time. It's a loose-loose situation.

They should read about the Agile Methodology:
http://en.wikipedia.org/wiki/Agile_software_development

Programming is not like building a car. We cannot compare a line-
production with software development, unless you look how the line-
production itself is build. Once it is build, it doesn't change any
more. A working line-production is like a boxed software: done and
ready to work.

Good luck....

On Sep 8, 7:28 pm, P Rouleau <proulea...@gmail.com> wrote:
> That's also what my thinking.
>
> that remember me a story about a company, maybe IBM, that switched to
> a strategy of giving bonus to the developers based on the number of
> code line created. It was supposedly a mean to measure productivity.
> It only resulted in code-duplication. The developers copy-pasted the
> code instead of creating nice functions and re-using them. They went
> back a few years later. Sadly, they wasn't alone to do that mistake.
> It discouraging to see something similar in >2010.
>
> Anyway, what's the value of 1000 lines of code per hour if they
> contains bugs that take days to find later. I prefer 100 lines that
> works. That's left more time to do more test.
>
> Really, you should update your CV.
>
> On Sep 8, 10:48 am, Cathy Shapiro <cathyshap...@gmail.com> wrote:
>
>
>
>
>
>
>
> > My solution would be to find a new job!
> > That's ridiculous. Obviously someone came up with the policy who has no idea
> > about programming.
>
> > On Thu, Sep 8, 2011 at 7:38 AM, Andy <a...@hardyfamily.org.uk> wrote:
> > > Clive,
>
> > > On Sep 8, 12:42 pm, Clive Crous <clive.cr...@gmail.com> wrote:
>
> > > > The company I work for sent out an email this morning instructing us
> > > > to, from now on, commit all source code changes for whatever we're
> > > > currently working on and push (to central
> > > > company git repository), regardless of the progress, status or state
> > > > every half-an-hour so that they see the
> > > > changes being made and can monitor productivity. Thoughts on this?
>
> > > Tee hee! Welcome to the 18th century and the joys of piece-work!
>
> > > Perhaps you should suggest that they install keyboard loggers instead
> > > so that they could count how many keys are being pressed!
>
> > > Unfortunately, it sounds like the idiot who came up with this idea
> > > wouldn't understand a rational discussion about the logic behind this,
> > > so I'd just go with the flow and create a script that modifies and
> > > checks in the same file every few minutes and then bask in the glory
> > > of being 'productive'!
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Git for human beings" group.
> > > To post to this group, send email to git-users@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > git-users+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/git-users?hl=en.
>
> > --
> > Flash Pro Design
> > 4646 Poplar, Suite 517
> > Memphis, TN 38117
>
> > Phone: (901) 767-8767
> > Fax: (901) 685-9054
>
> >http://www.flashprodesign.com

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to