Service Work: Towards re-shaping the Top Developers towards professionalism - page 15

 
MrGold166:

You do realise that this is nonsense, don't you?

A customer could break his leg, drown on the way to the hospital, end up being rescued and lying in a coma for a couple of years...

There's a deadline, there's arbitration, what's the problem?
 
sergeev:

There's a guy on the forum who has 20(!) unique ip. We still can't guess which one will be 21.)

Do not share the information, who is this "hero"? :)))
 
sanyooooook:
There is a deadline, there is arbitration, what's the problem?

The deadline is for the contractor, not the customer. You are either being silly here or you have lost part of the dialogue, you are talking nonsense.

 
abolk:

One thing that is not clear is how the "market" and "free competition" generates streams of orders at inflated prices - for $100, $200, $300, $400 for a task that is done in 1 hour or 10 minutes? When there are only one or two such customers, it is understandable. But when there are a whole queue of such customers? And when there is only one developer. Has anyone has seen a huge queue for clothes in an expensive boutique, and this queue is endless?

It's elementary. A man knows his business well and values himself above $10.

The customer is willing to pay for a lot - for understanding at a glance, for frankness, for responsiveness, etc. Find what they are looking for and you will have a queue lined up.

 
MrGold166:

The deadline is for the contractor, not the customer. You're either being silly here or you've lost part of the dialogue, you're talking nonsense.

Well you are complaining about the average 1-2 days of work, and the customer can stall, so I say, put a deadline of 2 days time is out arbitration, if right the work will be completed forcibly.
 
sanyooooook:
Well you are complaining about the average 1-2 days of work, and the customer can drag the time, so I say, put a deadline of 2 days, the time is out of arbitration, if right to finish the work forcibly.

You are talking nonsense, my dear. To submit to arbitration and forcibly complete the work just because the customer takes a long time to check the work? Are you out of your mind or what? Or are you writing from the wazoo what comes into your head just to get an answer?

First of all, the arbitrator will not do this and will wait for at least a couple of days.

Secondly, to complete the task forcibly, they will have to look into the task and check the code themselves. For this by the rules they can take the payment by the way, while never took, but if it will go so just start.

In third, you will spoil your relationship with the customer + ruin the customer's impression of the service because they will decide everything themselves.

Third, you will ruin your relationship with the customer + you will ruin the customer's impression of the service because he decides everything himself.

 
There are no tasks that can be done in an hour, don't humiliate yourself. The tasks themselves might be done in an hour, if it were all in the task itself. Everything together with the task is far from an hour. Think about how many people can be served per day, even with the most elementary tasks. The 3rd is the limit of one hell of a life.
 
Integer:
There are no tasks that can be done in an hour, don't humiliate yourself. The tasks themselves might be done in an hour, if it were all in the task itself. Everything together with the task is far from an hour. Think about how many people you can service per day, even with the most elementary tasks. The third is the limit of hellish life.
If TK is set clear, more than half of the orders (which are and were in the service) are performed in less than an hour. Of course, we are not talking about newbie progers who have just read a textbook.
 
MrGold166:
If TOR is set out clearly, more than half of the orders (which are and have been in the service) are executed in less than an hour. Of course, we are not talking about newbie progers who have just read a textbook.

Well, you can't tell by the deadline how long it takes to get them there. During this time, the customer can distract the contractor.

It's done in an hour. Are you saying that you are able to serve 8 customers in one working day and do this every day?

 
MrGold166:

You are talking nonsense, my dear. To submit to arbitration and forcibly terminate the work just because the customer takes a long time to check the work? Are you out of your mind or what? Or are you writing from the wazoo what comes into your head just to answer?

First of all, the arbitrator will not do this and will wait for at least a couple of days.

secondly, to make the compulsory completion, they will have to look into the job and check the code themselves.

thirdly, you will spoil the relationship with the customers + spoil the customer's impression of the service because they will decide everything themselves.

Read again what we are talking about and use your brain, please, before you write another reply.

I'm not complaining about the fact that the accounting time includes the time of the customer, I think it's legitimate, because the work is not just the participation of a programmer, the customer in any case, must check the work.

It is nonsense that the accounting time should not include the customer's time, but what do you lose from the fact that the funds will be transferred to 3-4 days later.

If it is so urgent, take the customer's contacts, the same phone number, and if you think it is ready, call him to agree on the completion of the work.

ZS: I'm all about the customer's time.)

Reason: