Service Work: Towards re-shaping the Top Developers towards professionalism - page 6
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Attempting to shift responsibility to another with the bravado of 'I deliberately turn my head off, rely on the contractor and demand 100% responsibility for everything from the contractor', brings imminent problems for the author.
In any case, for our part, we will increase customers' awareness of potential performers and prohibit them from recruiting a lot of work.
Attempting to shift responsibility to another with the bravado of 'I deliberately turn my head off, rely on the contractor and demand 100% responsibility for everything from the contractor', brings imminent problems for the author.
In any case, for our part, we will increase customers' awareness of potential performers and prohibit them from recruiting a lot of work.
... If the plan was 3 days, but the actual time is 7 days, then the customer will know that there is a high probability of failure.
Why the urgency? What's going to go wrong? Surely, once the job is received, the customer will be testing it for months. What difference does it make, then, if it's 3 days or 7 days?
Why the urgency? What's going to go wrong? Surely, once the job is received, the customer will be testing it for a month or more. What difference does it make, then, whether it is 3 days or 7 days?
:-) An unseemly statement in a software environment.... A deal is worth more than money.... there can always be two or more points of view on deadlines, a compromise is a mutual agreement to the mutual agreement of the parties, if the failure to implement the algorithm can lead to the failure of the program, then the failure to implement the agreement on deadlines can destroy the relationship between the contracting parties.... not always of course.... but it can...
It's a basic relationship algorithm.
Ideally, both contracting parties should be 100% responsible for the commitments made.
I pondered for a long time, a long time ago, about this kind of mathematics, because it adds up to 200% - if two parties agree and both take 100% responsibility.... and how can there be more liability than 100%
However it is so.... there must be something intangible interfering with the process of agreements...
This is not the first time I have heard about overdue orders and dissatisfied customers.
It is true that the programmer has no responsibility - you cannot even leave negative feedback for an order that has been cancelled (e.g. because it is overdue).
For me, the responsibility (financial or in the form of rating) would not be superfluous. But the programmer should specifically account for those periods of time he/she is responsible for. And in the status of "checked by customer" let it hang even 50 jobs.
It is a basic algorithm of relationships
Ideally, both contracting parties should be 100% responsible for the commitments made.
Everything is clear with programmers - whatever way you look at it, he is to blame for taking the order and breaking deadlines and ..... and that he worked, and as you know, those who do nothing are never at fault.
Then it remains to deal with customers, especially beginners - what is the customer's demand for the inability to formulate correct TOR and "blow your brains out a dozen times with its childish spontaneity. If you know that the 1st bar is the right one, then the Expert Advisor opens trades not in accordance with the indicator signals on the history - it strongly lags, it needs earlier.....
????????
Why the urgency? What's going to go wrong? Surely, once the job is received, the customer will be testing it for months. What is the difference between 3 days or 7 days?
The difference is that the "7 instead of 3" can be several: one programmer could not cope with the task and the contract was terminated, the second one could not make it in time and the contract was terminated again, etc.
And it is not a contractor's business to count customer's time (money). If you say 3, do it for 3 (clarification of the task and final verification do not count).
Everything is clear with programmers - no matter how you look at it, he is to blame for taking the order and for screwing up deadlines and ..... and that he worked, and as everyone knows who does nothing is never at fault.
Then it remains to deal with customers, especially beginners - what is the customer's demand for the inability to formulate correct TOR and "blow your brains out a dozen times with its childish spontaneity. If the first bar is the right one, then the Expert Advisor opens trades not in accordance with the indicator signals on the history - it strongly lags, it needs earlier ......
But the customer pays the price and cannot take anything else from him.
The developer decides whether to accept the job (and what price to set). If you want the job at any price - deal with 50 pages of nonsense description for $10, if you don't want - call it "$100 for writing an algorithm" and wait for your customer.
Besides, there are TORs and arbitration. "Severely delayed" has to be formulated, or it will be rejected.