I don't know too many of Ferris' investments, but the few I did know seemed like he would have to change the world almost to make them work. Whereas other investors might have a couple of moonshots like that, but they also have a bunch of investments that solve problems that people face right now, not ones they might face in the future.
I remember he was talking about those protein bars made out of crickets. And there is valid concerns about the future of food with synthetic meats etc. But cricket bars... I mean we are so far off from that being a mass selling product.
Just jumping on in terms of the "architecture" certifications. I'm currently doing the Azure architecture certification (And have the course materials for the AWS ones too). They are REALLY light on implementation. It's literally like reading a feature list of every single thing the cloud provider offers.
It's for when a question comes up like "Hmm. How can we we send a message that allows a yet to be decided amount of subscribers to act on that message? I know! Azure Service Bus!".
It's not that expensive to get the certifications so I usually say go for it. But it can be really dry and not as "real worldy" as you might expect.
So far it's very high level and "let's build a wordpress site in multiple AZs with an RDS instance and an ELB"
not "Ok - we have a site that gets millions of hits a day; currently uses 1 LB, 1 NFS shared file server and 3 web servers, and 1 dedicated DB server. Let's rip everything apart and move it to AWS with as close to 0 downtime as possible"
I just didn't want to go into this almost completely blind. The price of the exam is "negligible" (not to call $150 / exam insignificant - to some, I'm sure it's a lot) so... why not. I'll have a good base to start with when I finish and at least can speak to it where before, maybe I was speculating.
In Elasticsearch a "river" is the description for the pushing of data from your primary store (A database more than likely) into the elasticsearch index.
ES actually started with Rivers being part of Elastic but since deprecated it. You will still find people talking about "rivers" though as a description for however they are updating the index.
Is it really a ponzi scheme? Sounds just like any other startup mentioned here where they burn a tonne of cash while working out how to be profitable. Just because they don't make money now and there is a shortfall doesn't mean it will always be that way. Maybe they believe eventually prices will fall due to the volume, or people will continue buying membership but not use it as much etc.
The issue with this is that there are so many "grey" areas for different people. Google themselves don't really want you building links manually, they think that if you have good content, you will get links naturally and all will be right in the world.
At one point years ago I got half way through finishing an eBook/info product that was an SEO checklist. But half way through I felt that some people would find link building "spammy" no matter what. At that time, I was manually building large Web 2.0 networks with good quality content, and having it all funnel up to my main site. Even this can be seen as "grey hat" at the very least to some.
We've seen this come up a lot recently with Tesla's move to fine drivers who "park" at charging stations. Many see this as actually worsening the problem as people are happier to pay the (relatively small) fine.
I'd read both this article as well as the one about Tesla, but it never would have occurred to me to connect the two! So many aspects of behavioral economics seem counterintuitive at first (introducing penalties increases rule-breaking) but are obvious in hindsight (monetary penalties appear to reframe a calculation away from social decision-making toward economic decision-making, which can change the participants' conclusions toward the penalty)!
If the problem is people leaving their car there for hours, is a $24/hr fine really that small? Yea, it might increase the number of people who leave their car there for 10 extra minutes, but it seems highly likely to address the real problem, which is low turnover at the Superchargers.
Even then, Tesla can very easily just increase the fine (or do something like a steadily increasing fine) to address this concern. They could also charge additional fees to anyone who leaves their car at a supercharger for too long serially (and my guess is that these are the real problem).
Maybe they should setup an overage amount - e.g. 1 hour / month that you're allowed to park for free. After that every hour that you charge results in warning letters etc. eventually you aren't allowed to charge at any of the stations. Probably a little extreme but might work.
Yea, if, as seems to be the crux of one criticism of the policy, is that it allows bad actors to simply pay for the privilege of their bad actions, penalties that scale to extreme quickly is probably the best method. It's unfortunate, since the (very large majority) of good actors are also at risk of punishment.
I can recommend the book 'What money can'take buy' by Micheal Sandel. He has many more examples where using a fee actually resulted in an increase in the undesired behaviour.
Well yes because .net standard is simply the specification, and .net framework, mono, core etc are the implementations.
Think about it in a web sense. We have ECMAScript which is slowly being added to. ECMAScript is the specification and it has it's own version. Then we have browsers that "implement" that specification and they also have their own version numbers because they aren't ONLY building something to handle ECMAScript, they are building other features on top of that.
So in terms of .Net Core vs Mono for example, while they both may implement the .net standard, they can also have their own features unique only to one. It's not a straight implementation with nothing else added.
Now say you are building a website and you want to target all "modern" browsers. It doesn't matter what version of ECMAScript is up to, it matters what each browser has so far implemented. If you are building a library for .net, then you can say "OK, I implement this standard. That means Mono Version X and .net Core version Y can be used". Similar to how you would say "You need Firefox version X or Chrome verson Y to use this feature".
>On PaaS, it still makes a lot of sense to use Windows as the underlying OS
Why is this the case? I would have thought PaaS of all things would be OS agnostic as the end user doesn't really care about the OS or how things are being done in the background as long as it's simple to deploy/configure etc.
For example if Azure Websites suddenly made this big shift to Linux for some reason, it wouldn't affect anyone actually using the service.
The whole "mouse over a video and see 5 stills taken from the video" is a crazy good innovation first seen on pornsites (AFAIK) and it always blows me away.
I remember he was talking about those protein bars made out of crickets. And there is valid concerns about the future of food with synthetic meats etc. But cricket bars... I mean we are so far off from that being a mass selling product.