4,464 karma · joined June 22, 2009
Also I assume because it's a premium location that they rented or bought for that WeWork office, that their prices will also be premium. And honestly, if I can pay premium, wouldn't I just get my own office?
It all didn't really click together, so I never entered a WeWork office again. Instead it let me to wonder if the start-up world has reached it's peak.
Edit: To not just say negative things. The CEO of WeWork is a super smart business man. Another commentor posted an interview (https://www.youtube.com/watch?v=yOb_ogQJWeI) and I have to say I would also want to give this guy money. He's totally able to sell his vision as something that already exists and just needs your support to get it finished up.
Doesn't matter if government, company, NGO, newspaper, soccer club, church. Whatever offers power over other people has this disadvantage.
That's how this world works, and it's not like they really have a choice in that matter.
The problem with this whole situation since day one was: How can you be sure that you're not cheated if it's in the other side sovereign's interest when you get cheated.
So yes, there was probably never a point where you could have invested reasonably into Chinese bonds or stocks or startups.
Both Western and Chinese "fictitious overlay" to real market is so big that each can lose their current leadership position through that fantasy blowing up. In some regards the trade war is like this party game where you need to step on other people's balloon with your foot that has also a balloon attached.
The good news is, once one of the bubbles burst the other one can be exchanged step by step with real markets that are overtaken from the other.
It already sounds toxic. Instead of loading your page suddenly I load a google wrapper that includes some parts of your page. Doesn't that sound like a red flags for anybody? Does it sound less toxic if I call it "free and open google wrapper build on existing technologies"?
I see this in my corp every day. Very smart people, super interested in actual feedback, and super interested in really providing great software. But in the end they still fail. I'm not 100% sure about the reasons, but I have a guess.
Usually people who move up the ranks and get into positions where they can make decisions, tend to build relationships with other such people. So more and more they change from "why the hack is dns not working on server-13 anymore?" to "this is the big problem the market has, let's attack that". And slowly that thought croaches in that you should only think about the big picture problems and not worry about the nitty-gritty details of every day getting-things-to-run.
And that's probably the problem. While it's clear that you can't solve all the details and work on big picture problems at the same time, you should not devaluate the details. Great solutions solve big picture problems BY SOLVING THE DETAILS.
That's why K8S for instance is a mediocre solution. Sure they have great big picture ideas, but usually people spend their time with having DNS not working, having servers hanging, having etcd nodes not talking to each other without explaining why, having deployments say "SUCCESS" while actually not running. K8S provides a standardized API for every detail and every use-case, cool. But in the end you need to be an expert in everything to make it run around 50% of the time (outside of AWS and GCP). Nobody really wants to develop on k8s when the underlying platform is only available 50% of the time. And that's the current experience.
So please, if you are one of these people who is really interested in creating great software, consider finding solutions to the detailed low-level problems an important part of the goals and tasks you define. Usually the core low-level problems are not a big amount. For instance with k8s it usually is networking, dynamic storage or security related. Have one person in your team really become an expert in one of these areas (by checking out problems and solutions that exist, not just by making up ppt slides with plans that have nothing to do with the real world) and allow them to influence your task planning.
I bet you do it on AWS or GCP, right? Try on-prem, then check your headackes again. ;-)
a) re FaaS. Of course if you have an on-prem component, someone needs to take care of it. That's why it's on-prem. But still you can separate administration of that from the developers and have the additional new feature that you as admin don't need to care which software runs in these clusters. (In reality it's never that simple since specific hardware for the task outperforms the standard hardware by more than a margin, but at least you have to worry less about getting from cool-product:v1.0 to cool-product:v2.0 as admin anymore.
b) This dream of cross cloud portability needs to die
Well, you are either a cloud provider or a software/hardware provider that is not a cloud provider. If you are the latter of course you need a way to attack the cloud providers when everybody moves to the cloud. It's a common and traditional idea.
And at least for me it also makes sense to use such a solution. I would always go for Openshift (not working for Red Hat) since they are much better at getting on-prem to work than k8s, and you have the almost same setup and interaction experience throughout all your clouds. I hope so much that they can also find a way to more seemlessly work on arm and ppc now that IBM has bought them. Then it's truly hybrid.
PS: That said I also wouldn't trust any of these quickly assembled hybrid cloud solutions from companies who are not well known for their software achievements. It's probably only the marketing aspect that's driving these efforts and IBM has already shown that they don't trust their own solution themselves even.
An airplane can reduce the risk of falling down, but if you want to be protected(!) against falling down from the sky you shouldn't enter a big piece of metal that lifts off from the ground.
It's a super complex topic, it needs leadership support so that you can get a reasonable percentage of the community to drill down on one solution instead of having 4-5 competing ones, but it also needs a lot of in-depth insights, which is kind of opposite to leadership which requires a top-down view.
I don't believe anymore that this stuff is a new phenomenon though. It's more like a group of people trying to discredit university these days.
http://buddhistinspiration.blogspot.com/2011/12/well-see-zen...
What I already know is emotional pattern matching. E.g. one smells a spice that one's mother used as a child and one is immediately transferred back to that time. In that way if one recognizes that high excitement is often related to advertisements or scams one might recognize when one feels that way that something might be fishy.
Or what I also know is path recognition. E.g. "at first we did this, then we did this, then we did this, and therefore we arrived at X". In that way we can remember processes like riding a bike or our way home. That's also how memory palaces work.
That, I feel, is the hardest part of learning more about scams and how to protect yourself. You inevitably see a lot of people who simply can't avoid it, almost going for getting scammed like a moth goes to the lamp, never learning from bad experience that you simply can't get rich quick if you aren't already rich.
Will you, at this point, remember that "Scammers dress up ‘opportunities’ with professional looking brochures and websites to mask their fraudulent operations. They often begin with a phone call or email out of the blue from a scammer offering a ‘not-to-be-missed’, ‘high return’ or ‘guaranteed’ opportunity. The scammer usually operates from overseas, and will not have an Australian Financial Services licence"?
Probably not. But you might remember the story that guy on hacker news told you. You might remember, just as in that story, that you should look out carefully when a "great opportunity" arises. You might check your emotional state and find the comradry you feel to that old friend might not be based on facts since you haven't seen him for a long time. It's rather related to you two having a great night together.
And you might recognize that this combination of great offer, excitement, and a person who doesn't spend time with you often are combining to red flags for a scam.
But that is all because it was a specific example, a story. Not just a list of facts and attributes that generally relate to a set of scams that can be categorized as rather similar.
Therefore I'd argue that such a general list of scams, without specific examples, is not worth much. People's brain simply doesn't work like that. Rather check on Youtube for actual scams. Like "tourist scams in <countryX>".
If Linux would be a proprietary product, than post-acquisition-github would get a fix from Linux developers because Microsoft is big. Not Github would provide anything, but they would get something due to the size of the Microsoft empirial stamp.
So, Github owned by Microsoft might not even notice such a bug for long, since the engineer would be able to get it fixed through an email or two. While the pre-Github-purchase Gitlab might have gotten no fix at all.
In that regard one might argue that open source doesn't completely destroy the ability to solve problems, but open source certainly helps balancing out the odds for different competitors.