arasmussen

Sounds like a good answer to "When have you most successfully hacked some (non-computer) system to your advantage?"

Did you try logging in?

Lyft gives drivers a larger portion of the ride's cost (80% instead of 70% IIRC). I never feel obligated to tip, but tip if the service was great.

#bandaidfix

I left Facebook almost a year ago so I can't speak about Today.

But back then internal adoption of React Native was definitely accelerating rapidly and it was solving very real organizational and developer experience problems. The original motivation of the project internally was to solve developer experience pains, just like React but for mobile.

- With such a large app (Facebook), the compile cycle was becoming quite slow. RN has no compile cycle.

- You've got 3 teams (web, iOS, Android) per product (eg. Events, Groups, etc) and they don't really communicate or share any product code despite building effectively the same thing.

Take the Mobile Ads Manager app: Now one team (of web engineers) can ship an app on iOS and Android, while sharing 83% of the code between each app, in half the time the project had budgeted for just the iOS pure native app. Not to mention the team constantly loved their jobs because they didn't have to wait 5 minutes for the damn thing to compile every time they made a change.

> So degrade the experience just to make the product team happy?

Which part of "equivalent" did you miss?

You're entirely missing the point. This isn't about product experiences whatsoever. You can ship equivalently delightful experiences in React Native as you can in pure native apps. The point of React Native isn't to make your app more delightful.

The point is to develop it faster, in a more enjoyable manner, and enable one product team to develop for multiple platforms. This is an incredible win organizationally and for developer experience.

> Steve Jobs would have me fired

Check your ego.

There are definitely parts of the Facebook app built in React Native. I built some of them. :)

The point of React Native isn't to create a delightful product experience.

The point is to create the equivalent experience of a native app with a delightful development and organizational experience.

- Instead of having separate teams develop your iOS, Android, and now OS X apps, one product team can make all three and share the majority of the code.

- Instead of a slow frustrating compile cycle you get live reloading.

I totally would have used this last year when commuting from SF to Menlo Park. It's too bad I sold my car and quit my job, would have been fun to meet some cool people and make some extra money at the same time.

My friend is 7 feet tall and he mentioned to me that he fit better in my model S than almoat any other sedan.

Credit card worked for me for the S

Hi Sam,

What are some actions people like myself can take to push our community, nation, and world towards Basic Income?

This is particularly important to me because of how fast Uber/Tesla are rushing towards fully autonomous vehicles. Over 4 million jobs in US alone are as drivers. They're all gonna be laid off soon.

I think the term "self-driving" is preferable to "driverless" because it's not like there's no driver, the car is the driver. It's also less scary-sounding which could help speed up adoption. :)