Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I recall a story about someone at a government contractor who did a major refactoring and removed thousands of lines of code from a project, increasing its performance, only to be told by management that they'd signed a contract that said the company got paid by lines of code delivered, and his improvement would cost them tens of thousands of dollars, so revert the whole thing.


As long as we are counting LOC before compiling, that can be solved easily:

    if (false) {
      /* original code stays here, as we are payed by LOC */
    } else {
      /* write your new code here */
    }


Realistically, it would take some compile time conditionals in a bunch of places to get rid of the dependencies. The best part, you'll get paid for all those #ifdefs, whens and #[cfg()]s! You can even split longer functions to be able to wrap each one of them in those conditionals! Where do I sign up?


As long as this is contained to the metrics-metagame branch of the git repo, I am fine with this.

Get 80k commits in, before lunch.


That's a pretty bad breakdown in communication- the manager should have communicated how the contractor was paid and the programmer should have spent their time working in line with that - whichever end that breakdown happened on that sounds like that led to an awful lot of misery and wasted time - ouch


> That's a pretty bad breakdown in communication- the manager should have communicated how the contractor was paid and the programmer should have spent their time working in line with that

Seems

more

like

a

breakdown

in

negotiating

the

contract

than

a

breakdown

in

communication.

No

customer

is

actually

interested

in

having

the

programmer

do

their

work

in

line

with

a

compensation

scheme

that

pays

more

for

more

lines

of

code.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: