No, the distinction is that he had the option to remain at YC if he chose to. He could have simply turned down the offer from OpenAI. It's similar to receiving a job offer from another company... you’re not being dismissed from your current job. You get to decide whether you want to stay or move on.
I was thinking about this just the other day. If infinity isn't actually a thing in our universe, then maybe we're taking some risks by using math with all these infinite limits and integers. Maybe if we look at theorems without using infinity, we'd stumble upon new or different equations.
Hands down the best book I've read to level up my UI game. Highly recommended to developers who want to get better at UI design with no bullshit and a lot of practical examples.
Personally, I used to be very passionate about coding. but over time I've realized that I'm more excited about products/design and working with great people. I know that going into management is often frowned upon among engineers, but I personally love it because I can continue to work on products without constantly banging my head about compiler errors or annoying bugs. Basically, what I'm trying to say is that it's possible to be passionate about building products without having to sit and code all day.
Not that I care, but you could even copy the current twitter usernames to your new twitter, alongside all their public tweets and followers. So, when switching, a user wouldn't even need to add back their data or find back their previous followers.
Working on an offline/real-time library for agnostic backends. (Most libraries force you to go with a specific vendor like firebase/aws) or use a completely different backend/db (like couchdb/pouchdb).
Personally I really enjoy his writings on all kinds of subjects (coding, political, parenthood, startups, etc.) He's the main reason I did a startup and joined YC. I'm still a bit sad I didn't get to talk to him while I was at YC.
I don't particularly like Apollo, but the reasoning is that if you fetch data with Apollo on the client-side, then that data is already available in their cache. If you were to use Redux, you'd have to copy that same data in your store.. so might as well use their cache instead. However, this is only for fetched data, not all client-side state management.
Personally, I don't like the "write client-side resolvers mimicking the server resolvers" approach. I'd much rather have a database that is synched with the server and listens for new changes. Once you have your "offline-synched-db", you get offline, optimistic-UI & real-time for free.
Yeah.. Ideally you can find a job that plays to your strength. If you don't like and aren't good with this type of work, it's probably a sign that you should focus on something you find easy and like. It's easy to be good when you really enjoy something