A broader one: writing expressions as much as possible. Basically, it means avoiding unnecessary mutations (and jumps).
Then avoiding architecture. Thinking algorithms that process data (instead of "systems") has been transformative.
14 karma · joined August 6, 2019
A broader one: writing expressions as much as possible. Basically, it means avoiding unnecessary mutations (and jumps).
Then avoiding architecture. Thinking algorithms that process data (instead of "systems") has been transformative.
What's to understand here is that it's not said that this killer app "exists". If VR is only a cooler screen, then it will sell like cooler screens. Now maybe it's a killer screen, that is a screen that everybody wants. I guess there is a competitive advantage of thinking like that, but right now, vendors think they are making a software/hardware platform when they have no killer app.
There might be in the CRs you're mentionning. In other words, my advice would be to get the most out of those CRs as you can. Ask questions, encourage people to be critic with you, understand their point of view and learn. If you CR is rejected, get to the core of why it happened technically.