3 ms·
"You should have it by 7:05 pm PST." -- From one of the examples. I have uneasy feelings about this. I know that you're targeting grunt-jobs and it's easily e
by dyadic 12y ago
"You should have it by 7:05 pm PST."
-- From one of the examples.
I have uneasy feelings about this. I know that you're targeting grunt-jobs and it's easily estimateable. But I also know that things happen and they can't always be met.
If I'm going to send out a grunt-job then more often I care more about it being done well than being on time. If you're targeting quick turnaround over correctness then I imagine that I need to spend more time verifying the work, exactly what I don't want to be doing.
- siddboots 12y agoI had the same reaction to the examples. Even for "grunt-jobs", I would be extremely sceptical of anyone who can give me an ETA after thinking about the problem for less than five minutes.
- drawkbox 12y agoAgreed, these services or even outsourcing can sometimes lean towards getting done just to have it done by the date than by actually being complete with the task. I have actually worked with people before that turn in projects incomplete just to have it in by the business due date, then later say sorry it has this or that bug. They do the pretend it is working dance. Services like this tend to be the done rather than complete type of programmers unless it is an easily verifiable task. Any programmer knows, there are many stages of done and only one complete. Is your developer you get a done type of doer or someone who completes something?