Or downvote until the score is zero. I.e. don’t allow negative scores. Then take reputation away from people who actively attempt to downvote beyond zero. In addition, you use reputation to downvote.
Let’s remember that score is not money, and many people actually do not care if reputation is reduced by automated means (as opposed to someone’s view on their acting). Score is just a raw signal to a participant on whether they did good or not. It never was a “win all the score non-decreasingly” game. If you spend 30% of your 10k on downvotes, it is still credible 7k. And if you gain 10k and see 3k problems, then these are community problems indeed.
My guess is that downvoting costs score only to weed out low-score inexperienced accounts from emotional voting or manipulation. No effort no score. No score no downvotes. –> no effortless misbehavior. That’s it.
I just got more and more frustrated reading the README because I kept thinking this has already been done brilliantly and in multiple languages. It’s called What3Words.
Familial status is off limits in the US. So is marital status, health questions and questions about transportation to and from work. Basically, if it isn’t related to the job you could find yourself embroiled in a nasty lawsuit with the Labor Dept. not on your side.
Yeah, I’m living in my dream house but it cost me less than $500k. When I saw the first example was a $3.5 million home I stopped reading. It’s simple to spot people overbuying (read: guessing wrong). There are lots of people living in their dream homes they’re just not living in multi-million dollar homes.
That’s theoretically possible now if not actually implemented already. AMP in the email isn’t going to automatically make this possible. The SWA devs and the Delta devs and the AA devs and the Alaska devs and the Northwest devs, ad naseum are all going to poorly implement their version just as poorly as their REST version (if they have one). The implementation mechanism isn’t really going to improve the experience. It will just be something different that is broken or slow.
Pensions and other benefits run about 36% of base salary nationally (meaning it could be higher or lower for IBM). College grads aren't usually vested in their pensions, so they may be paid higher salaries and net a lower expense to the company. What's aggravating (especially from the younger posters) is the assumption that older people aren't/won't stay current. Currency is a dubious argument, if you're wedded to an older product, the new stuff doesn't benefit you directly on the job. After that comes quality/rates of errors. Younger employees tend to make hard-learned mistakes long after the older engineers have learned the same lessons. So cost/value isn't the same when comparing older and younger engineers. In the "real" engineering fields, younger engineers are universally required to work directly under licensed (read: older) for precisely this reason. It prevents preventable mistakes.
The best way to cancel any cable service is to simply unplug your equipment and drive to the service office and plunk it on the counter while announcing loudly that you’re canceling your service. It took all of 15 minutes and all the service rep said was “Sorry to see you go.” No retention techniques, nothing. It was the best customers service experience I ever had with Comcast.
In my experience helping an elderly relative with the cable shitshow, the Comcast service center people are actually really nice and would have done so without the drama. But I definitely recommend the physical side of things.
Although I have done a bit of a chaotic neutral thing myself: Comcast sent her two new boxes instead of one after we switched her to a cheaper box. They wanted us to drive all the way back to service center. Grabbed their UPS account # from the tracking code, filled out the web form and had it sent back with pickup billed against Comcast’s acct. She never got billed a cent.
