nijynot

While yes, that would have been a better title in terms of telling us what the post was about, but then you get a different tone for the post.

I think the post is first and foremost for thanking Arash for his work on Dropbox and about the partnership he had with Drew, and telling us about it comes second.

Here are my predictions:

1. Countries and private companies will launch stablecoins and it'll be the most used payment medium in developed countries.

2. Bitcoin will grow, but it'll not be the biggest cryptocurrency anymore.

3. Total market cap of all cryptocurrencies (including stablecoins) will be ~$8T.

4. Around 50% of the software jobs will be remote.

5. USA and China tradewar will turn into something more scary and people will be increasingly more wary of a third world war.

6. Apple releases their first iteration of AR glasses and it'll use an iPhone as it's driver.

7. Renaissance of piracy through decentralized systems like Filecoin. We'll have illegal products that will be easier to use than Netflix, and more content. Netflix, Spotify, et al. will never be able to have a complete library of all content, but it's pirate competitors will.

8. OpenAI will start building products or provide services for consumers or businesses. They'll be very profitable and have a valuation of around $30B.

Libra is not all that bad. While there are problems with Facebook gaining yet another source for information that takes advantage of privacy terms, I think a stablecoin by GAFA is in the right direction. It speeds up the adoption of cryptocurrency by a lot.

Paypal and other "digital cash" solutions are fully centralized which makes it impossible for devs to build on top of their platform. This means that problems that arise cannot be solved by devs looking at the problem from the outside.

Libra gets around this by having an open platform that anyone can build on. Anyone can create a Libra wallet, and anyone can build Libra services. If we have a big privacy problem with Libra in the future, we might be able to find a way around it. Libra supports scripting on-chain which would make atomic swaps possible. If something like atomic swaps are possible, can we hide information from Facebook et al? Or what about mixing Libra on-chain?

Definitely states the right problems, but not the right solutions.

The commits box is also bigger than the files box, which doesn't make much sense. Whether a commit box even should be there is a big question. How useful is commits to the average developer browsing a repo? I think a bit useful, but not useful enough to have 1/3 of the screen width.

Stats of a repo is pretty nice, because it gives an overview of how active it is, etc. But the problem is that majority of GitHub repos are empty and not that active, so it'll make most of the repos look like ghost towns. Not something you'd want on your site.

Moving all git tabs into the GitHub tabs makes it even harder to use the UI. You have to spend way too much mental load just to find the right tab to click on. It looks better, but will be harder to use.

The "Watch" button, moving description and tags is an improvement, and I'm for a redesign of some sort.

It exists, it's called https://earn.com/. You pay in cryptocurrency, but it works.

What use is equity if the company never goes public or never gets acquired?

Tokens can on the other hand have value even if none the above happens, and you get a liquid market much earlier. If the monetary policy of the token is reasonable, and the market cap shoots up for one reason or another in the future, you'd make a big buck.

But would you make any money on your equity of the market cap of the token would go up? Not necessarily.

I think "intersting" is often a bad rule too, especially if you've just begun reading. At the beginning, you don't have any kind of benchmark or reference for checking if what you're reading is good or not, and will therefore most likely accept anything as truth or insight.

If you've read enough on the other hand, then sure, it might work. Might in the sense that with some luck and taste, you'll find the good books. But it's still reliant on taste, which is very, very biased. Anything that looks uninteresting, but is awesome will be missed.

Medium actually does this.

One thing that came to mind is that some of these "13 thoughts" are kind of dependent on each other.

For example, you might not want to be bold and have too much self-belief without being able to work hard, think independently or making it easy for yourself to take risks. If anything, try to do all of them, or be wary of how you pick and choose from the list.

Jack Ma.

I don't agree with almost all of it. If you compare a normal wristwatch with Apple watch w.r.t time keeping only, you're not comparing it fairly. The Apple watch can just do so much more than a normal watch can, and it's programmable, you can add things with time. Same can be said for the alarm clock and what not. Why no compare a smartphone to the analog alarm? That'd what most people use I think, and they instead pick some gadget alarm clock which not many use I'd say.

A big difference is that a smartphone and Apple watch is a device that can a do what a 100 "dumb stuff" can do. It's a all-in-one device and that's very valuable.

Their last point on touch screens in cars is very weak. With a touch screen, you can change the UI anytime. It's flexible with infinite buttons. A normal one with real buttons sure are more tactile, but when you ship it, it's set in stone with limited button and functionality.

Check out this article [1] (or video) on Dan Schafer's talk, on how they use Dataloader and GraphQL internally at Facebook. Covers most of it.

To summarize, they create a class for each GraphQLType which has their own "gen" function such that it is the only way to generate data. This way you get a single source of truth.

There's also a video of Lee Byron going through Dataloader's source code which was pretty fun to watch.

[1]: https://dev-blog.apollodata.com/graphql-at-facebook-by-dan-s...

The solution for authorization/access control is to use "Dataloader" [1] which is also made by Facebook. You write a single source of truth for how authorization is handled, and make sure that graphql resolves with this source.

Dataloader is not as well known as GraphQL, but crucial for complex authorization systems imo. It also has a bunch of other features like batching and caching which makes your life easier when opting for this solution.

[1]: https://github.com/facebook/dataloader

Then you need to validate, authorize, etc. queries correctly. I see no reason why anyone would want this.

Instead use GraphQL which is a thin layer, and hide all the business logic behind it. Way more manageable.

Just to pick something more unusual, my Porter-Yoshida & Co. waist bag.

Women can carry a purse and keep all kind of things in it, but for men it's not really the same. Where do I keep my wallet, pack of tissues, some band aids, keys? A backpack is way big, too burdensome and overkill in most cases. That's why a waist bag is so perfect, it's the right size for kindle, keys, wallet, etc. and is low profile. Though I don't wear it as a waist bag, but diagonally from my shoulder.

But why not buy a single smart watch and keep your clothes normal? I mean, it's seems redundant to make every single piece have similar tech functionality when you can have one watch that works with all clothes. If you choose to have different tech in different clothes, I don't see why you don't want to combine everything into a watch. Though there are edge cases where you can want to split it up. But then your customer base gets much smaller.

Why get this denim jacket when you can get an iPhone and an Apple Watch?

Jacquard only puts limits on you as it's stuck on that specific denim jacket. Apple Watch on the other hand works with any jacket. You don't even need a jacket with Apple watch, you can wear whatever you want, whenever you want, and it would still work compared to Jacquard which wouldn't.