shawnhimself
Member
For those of you on your own - how are you estimating hours on program design?
I've heard of people basing it on the I/O count but that doesn't seem practical to me. When you start adding packML, motion applications, etc... the I/O count could be low but the design time certainly does not get any smaller.
I've recently started on my own but its been just 'hey do this and give me the bill' but now I need to provide an estimate to bid on a job... and frankly I have no rule of thumb on the hours it would take.
I do know that it will physically take more hours to do than I will ever estimate, but that's just me, overly meticulous at times. I chose not to bill people for my lunacy.
I've heard of people basing it on the I/O count but that doesn't seem practical to me. When you start adding packML, motion applications, etc... the I/O count could be low but the design time certainly does not get any smaller.
I've recently started on my own but its been just 'hey do this and give me the bill' but now I need to provide an estimate to bid on a job... and frankly I have no rule of thumb on the hours it would take.
I do know that it will physically take more hours to do than I will ever estimate, but that's just me, overly meticulous at times. I chose not to bill people for my lunacy.