tedd's Friday Post ($ per line)
in [General]
|
Prev: daemon
Next: Class mysqli not found
From: Robert Cummings on 7 Oct 2010 15:04 On 10-10-07 02:04 PM, Joshua Kehn wrote: > In the case payment does come down to lines of code written I'm already covered. > > if( count> 5) > { > /* Bracing Style > } I hope your $count var is being incremented properly under this model: <?php function increment( &$count ) { $count = 0; if( $count == 0 ) { $count = 1; } else if( $count == 1 ) { $count = 2; } else if( $count == 2 ) { $count = 3; } else if( $count == 3 ) { $count = 4; } else if( $count == 4 ) { $count = 5; } else { throw new Exception( 'Increment out of bounds' ); } } ?> Just think how much money could be made if you need to support large datasets!!! CHAAAAAAAAAAAAAA-CHING! Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized.
From: tedd on 7 Oct 2010 16:51 At 6:50 PM +0100 10/7/10, ash(a)ashleysheridan.co.uk wrote: >Surely it would have been a bit more sensible to work out the time >the programmer had spent on the project and then calculate it as a >percentage of the total time that programmer would spend on it to >complete it (which might not be the whole duration of the project) > >Also, counting code lines seems unfair. I know it used to be this >way, but its a bit like paying firemen based on the number of fires >they put out; don't be surprised if arson figures go up! > >I would guess though that this fellow likely had to pay some of that >initial outlay of cash back though, and would further assume the >total price attributed to each line was no more than 3 or 4 cents >(damb English androids don't have the cent character) > >Thanks, >Ash As I said, this was a case that I worked on several years ago (20+). I was not the programmer, but rather a consultant for an attorney. The programmer wanted to have his payment based upon the hours he put it, but the client wanted proof of the programmers effort. Both were understandable positions. Considering that the programmers effort did not work, and there were no time clocks showing the actual hours the programmer worked, the solution centered on an evaluation of the end-product. That evaluation reduced to the amount of code written, which boiled down to lines of code. Granted, as Rob said, some lines are worth more than others, but overall a case was made to pay a certain amount per line. Now, back to the question at hand -- what price would you sell a line of your code for? Cheers, tedd -- ------- http://sperling.com/
From: Joshua Kehn on 7 Oct 2010 16:53 $100 a line. If you want more then one line let's meet and go over the project. I might give a significant discount. Regards, -Josh ____________________________________ Joshua Kehn | Josh.Kehn(a)gmail.com http://joshuakehn.com On Oct 7, 2010, at 4:51 PM, tedd wrote: > At 6:50 PM +0100 10/7/10, ash(a)ashleysheridan.co.uk wrote: >> Surely it would have been a bit more sensible to work out the time the programmer had spent on the project and then calculate it as a percentage of the total time that programmer would spend on it to complete it (which might not be the whole duration of the project) >> >> Also, counting code lines seems unfair. I know it used to be this way, but its a bit like paying firemen based on the number of fires they put out; don't be surprised if arson figures go up! >> >> I would guess though that this fellow likely had to pay some of that initial outlay of cash back though, and would further assume the total price attributed to each line was no more than 3 or 4 cents (damb English androids don't have the cent character) >> >> Thanks, >> Ash > > As I said, this was a case that I worked on several years ago (20+). I was not the programmer, but rather a consultant for an attorney. > > The programmer wanted to have his payment based upon the hours he put it, but the client wanted proof of the programmers effort. Both were understandable positions. > > Considering that the programmers effort did not work, and there were no time clocks showing the actual hours the programmer worked, the solution centered on an evaluation of the end-product. That evaluation reduced to the amount of code written, which boiled down to lines of code. > > Granted, as Rob said, some lines are worth more than others, but overall a case was made to pay a certain amount per line. > > Now, back to the question at hand -- what price would you sell a line of your code for? > > Cheers, > > tedd > > > -- > ------- > http://sperling.com/ > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >
From: Bastien Koert on 7 Oct 2010 16:53 On Thu, Oct 7, 2010 at 4:51 PM, tedd <tedd.sperling(a)gmail.com> wrote: > At 6:50 PM +0100 10/7/10, ash(a)ashleysheridan.co.uk wrote: >> >> Surely it would have been a bit more sensible to work out the time the >> programmer had spent on the project and then calculate it as a percentage of >> the total time that programmer would spend on it to complete it (which might >> not be the whole duration of the project) >> >> Also, counting code lines seems unfair. I know it used to be this way, but >> its a bit like paying firemen based on the number of fires they put out; >> don't be surprised if arson figures go up! >> >> I would guess though that this fellow likely had to pay some of that >> initial outlay of cash back though, and would further assume the total price >> attributed to each line was no more than 3 or 4 cents (damb English androids >> don't have the cent character) >> >> Thanks, >> Ash > > As I said, this was a case that I worked on several years ago (20+). I was > not the programmer, but rather a consultant for an attorney. > > The programmer wanted to have his payment based upon the hours he put it, > but the client wanted proof of the programmers effort. Both were > understandable positions. > > Considering that the programmers effort did not work, and there were no time > clocks showing the actual hours the programmer worked, the solution centered > on an evaluation of the end-product. That evaluation reduced to the amount > of code written, which boiled down to lines of code. > > Granted, as Rob said, some lines are worth more than others, but overall a > case was made to pay a certain amount per line. > > Now, back to the question at hand -- what price would you sell a line of > your code for? > > Cheers, > > tedd > > > -- > ------- > http://sperling.com/ > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > <Dr Evil Laugh> One Beelyon Dollars -- Bastien Cat, the other other white meat
From: Nathan Rixham on 8 Oct 2010 11:30
tedd wrote: > Now, back to the question at hand -- what price would you sell a line of > your code for? Interesting case and question Tedd! Quite sure we all realise the answer is not black and white but various shades of grey, and I wouldn't fancy doing this for real - however, given the assumption that it was technically solid code "average", and assuming it was a functional approach (as in there wasn't chunks of domain schema classes with nothing but getters and setters around / boiler plate junk), then: 35-40 cents per line The approach I've taken to working it out is to try and average out lines of code produced per 8 hour working day, allowing time for research, decision making, minor code reduction and refactoring, then adding a small offset for any time spend on documentation which would show further understanding and confidence in the code + make it more usable. Whitespace and a coding styles which produce more lines but the same amount of code not included. I've also made a small adjustment for the 'several years ago' all though I'm assuming this to be early 2000s and not the 1970s ;) Anywhere near? ps: tedd, please cc me in to the final answer as I won't have time to check the list for a while, and I'm quite interested in this one - kudos to you if you managed to do it and get both parties happy with the result though! Best, Nathan |