Comment Re:The other real enemy: logic (Score 1) 589
I think you get to point to 60s-80s movie villains *or* suggest that the other guy has been living under a rock.
MVP and F2P eventually passed into regular industry jargon along with a boat load of other terms. Most every company involved in the space now talks about DAU, LTV, ARPU, ARPPU, ARPDAU and even ARPPDAU. They talk about performing cohort analyses. Some of them ask whether they are working on an MVP or an MDP? Most don’t really bother discussing viral K-factors any more, and instead obsess about the CPA of players. These are significant changes for an industry that used to worry more about Metacritic ratings.
Jesus, some executive just had a seizure on that guy's keyboard.
To translate things into terms that the slashdot audience may have an easier time understanding: The failure to reproduce a software bug on the programmer's system is hardly evidence that the software is fine.
It is still quite possible -- even likely -- that the software bug, or flight computer anomaly, is not caused by what the user thinks it was caused by. People are very good at finding patterns, but that includes spurious ones as well as real ones.
Although this is absolutely true, I hope you'll agree that it's not -- by itself -- a good reason to go out and do the thing you think might be causing the problem. It's certainly why we should keep looking for a definite culprit.
That's not a problem. You would never do any of this on the client end. It's far too easy for someone to strip out the hashing the password stage and replace it with a false "yeah, it worked" signal. Sony did a howler where they implemented a client side CAPTCHA where they sent out the right answer and asked if you'd typed it in. http://cryptogasm.com/2011/07/sony-captcha-fail/
It's might be 1000x slower but, so what? You can afford to take half a second longer. Users generally won't even notice.
He has not acquired a fortune; the fortune has acquired him. -- Bion
