158 karma · joined July 7, 2019
I think you're missing the point. He's saying we should work toward creating a new kind of technology where the ipad would really feel like a piano when you're on the "piano app", but feel very differently for other apps.
What you're saying is that you don't think that such technology could ever exist; BV thinks otherwise and he's working toward that vision. He's also saying that we shouldn't take the future for granted as if a technology will just suddenly appear. It takes hard work, funding and a clear vision.
I can think of a few ways about how we could add tactile touch to a dynamic interface (I.e. turning a piano 2D screen to a real experience). VR is going in that direction (to see 3D from a 2D screen) and you can imagine some sensors at the tip of your fingers where depending where you touch you'd feel something different. Again, that's just an idea, there are many ways it could be achieved.
On the front-end, I'd do a call to the server. On the server, I'd use a database transaction for that.
But I get your point. The way I deal with race condition in redux is to have a mutex. I.e. While something is being fetched, any call to this command is either ignored or queued up.
I use redux-saga for the "race-condition" and general flow, and call the various async functions from within sagas.
>> in an electronic circuit, what is a qubit?
It's not an electronic circuit, it literally is an electron or a photon. And it's using that particle's properties to do "superposition and all that jazz".
You can't put too many next to each others because they start interacting together because that's what electrons do when they get close.
>> that can hold more than 2 states
--> that can hold more than 2 states AT THE SAME TIME (in weird quantum conditions)
So you're not trying 00, 01, 10, 11; you're trying [00|01|10 |11] at the same time, as well as other state in between 0 and 1.
Yeah, and also at some point, it won't matter what's ideal or not.. it'll be about survival.
Spent a whole week on it because the questions were really good and had to do a lot of thinking and research.
> Do you need traction to get into Y Combinator?
At its core, to get in YC you need an insight to build something that has the potential to be a $1B+ company. Having traction is great because it shows that this insight is grounded -- but this isn't required.
If you have no insight and no traction, then you need something else exceptional to convince them to invest in you rather than the idea.
> What are some tips for writing the written application?
Don't bullshit and get a founder from YC to review the application. Unlike most people, you don't need to "bullshit YC" to get in.. they actually want to fund you as long as you can prove that your insight is grounded and made significant progress relative to where you were a few weeks earlier. Also, be concise because they're reading thousands of applications.. if as the CEO you can't be concise, it's kind of a red flag against you that you won't communicate properly to customers, employees and investors.
> Bonus tips on how to get into Y Combinator
Don't read too much into "How to get into YC" things. Be ruthlessly focussed on working on your product and talking to users. Better to fail fast and move on to a different product if users don't love it or you're not solving a major pain point.
This is my biggest pet peeve with junior developers. I find there's a total lack of ownership about making sure the feature is completely wrapped-up (not just the code, but the tests, the metrics, that it's shipped, that it's correctly marked as done and communicated, etc.)
I find they /expect/ that someone else at the company will review and make sure everything is done and safe, rather than be proactive about it.
200 000 000 users * $1.
Usually:
- biography or fiction book that I listen to while driving
- hard science book when I know I can focus for a few hours. (I.e. Quantum mechanics or advanced algorithms)
- 1-2 business or technical book that I read on kindle (Either from PC, ipad or my iphone)
- various blog or pdfs open on my pc / iphone
The business / technical books are the ones that I read the fastest because I can skip useless chapters and they're always one-click away when I have a few minutes to wait.The hard science are the ones that take the most time.. sometimes it can take me weeks to read a few pages, and I often need to do side research to understand what I'm reading.
I think the fact that I have different choices help me read more because if I'm not in the mood for one thing there's usually something else interesting. If I don't have interesting books then I'm more likely to waste time on reddit / HN / twitter. (I still browse HN from time to time when things are compiling though :D)