> You are paid based on how difficult you are to replace
May be true in general but definitely is unrelated to location based pay (wouldn't it be easier to higher another faceless IC in the bay area than in OKC?)
Somewhat unrelated but Citi's software has been ... not very good from my perspective as a customer. The app is crashing/down frequently, as is the website.
Mumble is pretty crummy for text chat from my experience. I still use it for voice on a fairly frequent basis, but having very ephemeral text logs (on client restart), and a lack of pinging users makes it a huge pain to use for text.
Also I'm not sure how useful it is to test people on remembering minutiae of a system on the fly. How often are you correct about small details of a system you work with on a daily basis on the first try?
Mine is 4.77, though I don't use uber that much. I'm also pretty sure they display a recent average, with old (>1 year?) rides not counting.
I also feel compelled to give drivers 5 stars because people IMO tend to look down at anything less than the best. I realize it's not the most accurate comparison, but would you buy from an ebay/amazon reseller who had a 80% approval rating?
> 2. Give them a playground to fail - Offload any non-business critical tasks and let them make mistakes. No one I know ever learnt programming without making any mistakes. Immediately tell them about best practices and how to avoid such mistakes in future.
I think even more importantly is to encourage failure, or at least reporting it. How many times have you been ecstatic that you managed to get a program to crash differently? A lot of people are terrified of failure, but people probably learn better from their mistakes. And showing them that it's ok (even encouraged) to report what their stuck on to you means that they can potentially get a quicker solution, learn from you.
May be true in general but definitely is unrelated to location based pay (wouldn't it be easier to higher another faceless IC in the bay area than in OKC?)