The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Yep, I heard bassoon as they turn 21, they start doing cello shots.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
probably why many watch it in secret (parents not looking) on youtuba
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
A contract developer has mentioned the below on the timesheet :
"Tested full workflow, identified bugs & fixed" - 16 hours.
When we expect a module to be developed, and we are outsourcing it completely, the expectation would be to have it working out of the box. Don't know how these bug fix routines could be added to the invoice. That's how this works? This is sounding crazy to me.
We don't outsource work much. Just learning these. I guess the contract document has to be tweaked.
Well, it sounds like you didn't get a flat rate bid from him.
Your option is this: if he blows past his estimate you might want to start to question the billable hours and he might work with you on that, but the fact is that it looks like he's being straight with you about what he's doing, and that's a good thing from a contractor.
If you seriously think he's trying to milk the contract, take a close look at what your escape clause looks like. Those things exist for a reason.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
That is not a contract, as you say, it is an estimate. You need to expect the cost to over run any estimate when creating an application and testing, documentation and training are the areas that are usually not included in the estimate.
Unless it is a trivial module then 16 hours seems to be a reasonable excess.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
"bug fixes" are are part of the dev process if it hasn't been released yet
I guess the "estimate" model wouldn't work. They can arbitrarily stretch it to their favor. What if he adds 32 hours on a bug fix tomorrow? saying it's a tricky, critical bug? We dont want to get into how he introduced a bug & fixing it. It should be internal to him.
A fixed cost deal would've been a trouble-free one.