3 ms·
It is harder to build trust when you don't see and hear the other party. I totally get that and its fair honestly, a lot depends on facial and verbal cues. So I
by uhxvt 5y ago
It is harder to build trust when you don't see and hear the other party. I totally get that and its fair honestly, a lot depends on facial and verbal cues. So I assume someone in my shoes would have to make extra sure to build trust by being responsive and delivering reliably.
It would probably also be beneficial to have some kind of proof that the work I claim to do currently is actually done, maybe invite the other party to the git repos or something. So if they wanted to, they could check on the status any time. I guess that might reduce some uncertainty.
- ilaksh 5y agoRight I mean you said you can't respond immediately but that doesn't mean you can't be relatively responsive as long as it's within a few hours or a day and you read and reply thoroughly and show evidence that you are making progress. I normally do give people access to the git and also regularly deploy. Also I pre-authorize X days or a week of work and don't continue until I get paid for the last chunk. That way both parties are seeing real things happen routinely -- software delivery and payment. Rather than for example having a two month long project with one payment and the website only really does anything useful at the very end.