I believe this is key. If more folks at more organizations were brave like this and willing to take the risk, a good chunk of the problems our civilization is facing might be greatly improved.
241 karma · joined March 28, 2018
I believe this is key. If more folks at more organizations were brave like this and willing to take the risk, a good chunk of the problems our civilization is facing might be greatly improved.
The items I put down in my comment are based largely on user reports, though (there isn't much else to go on). And I mean these items as questions (i.e. "is this accurate?"). Folks here on HN have definitely been reporting ongoing problems and seem to be suggesting that they are not resolved and are actually larger in scope than the Google blog post addressed.
Someone from Google commented here a few hours ago indicating Google was looking into it. And other folks here are reporting that they don't have the same problems. So it's kind of an open question what's going on.
I'm in the evaluation phase too. And I've found a lot to like about GCP. I'm hoping the problems are understandable.
1) For three whole days, it was questionable whether or not a user would be able to launch a node pool (according to the official blog statement). It was also questionable whether a user would be able to launch a simple compute instance (according to statements here on HN).
2) This issue was global in scope, affecting all of Google's regions. Therefore, in consideration of item 1 above, it was questionable/unpredictable whether or not a user could launch a node pool or even a simple node anywhere in GCP at all.
3) The sum total of information about this incident can be found as a few one or two sentence blurbs on Google's blog. No explanation nor outline of scope for affected regions and services has been provided.
4) Some users here are reporting that other GCP services not mentioned by Google's blog are experiencing problems.
5) Some users here are reporting that they have received no response from GCP support, even over a time span of 40+ hours since the support request was submitted.
6) Google says they'll provide some information when the next business day rolls around, roughly 4 days after the start of the problem.
I really do want to make sure I'm understanding this situation. Please do correct me if I got something wrong in this summary.
I would really like to see people rallying against many more things like this.
I myself started my first business at a time when I had virtually no money in the bank, and my car was literally repossessed one month before my business became profitable. If I had stopped and said "I can't afford this" and just given up and gone to get a job, I would have never seen the success that came later.
Also, you point out particular entrepreneurs who came from rich families. You completely leave out the wide array of entrepreneurs who did not. John Paul DeJoria, for example, was living on a friend's property because he was homeless and had almost no money. He started his business in those circumstances. He's estimated at somewhere in the ballpark of 3 billion net worth presently. There are quite a few stories of people with virtually no money building empires out of the rubble.
While I agree that there are a number of factors that feed into whether a startup is successful or not, I would kindly submit to you that one's attitude towards whether or not it can be accomplished is a very massive part of the picture. It takes focus and determination to get most businesses off the ground. Once you begin listing the reasons you can't accomplish it, you've begun setting up the circumstances such that you won't.