deboflo

Can’t get much less verbose than cloudformation yaml in combination with usage of only required parameters for a resource. For example, write a cloudformation yaml template that creates an automatically named S3 bucket.

The changesets feature of cloudformation allows users u to do most of what you mention here. Also take a look at resource deletion policies and Lambda custom resources.

You should take a look at AWS Code Pipeline, which natively support creating/updating cloudformation stacks.

“Chuck Norris can kill you. Jeff Dean can kill -9 you.“

“Jeff Dean once shifted a bit so hard it ended up on another computer.”

Yawn. You know Tesla isn’t just a car company, right? They are an energy company as well. They have people building out the supercharger network. Software engineers writing autopilot software. Employees working at Tesla sales centers. Tesla is not structured like a traditional automaker. Stop trying to compare with false metrics.

Once, in early 2002, when the index servers went down, Jeff Dean answered user queries manually for two hours. Evals showed a quality improvement of 5 points.

us-west-2 (Oregon) is still up for me from the CLI.

Seems crazy, but is actually a smart move.

I own 3,000 Tesla shares. Purchased most shares at $30 after driving my model s from the factory. I have seen my net worth get cut in half when tsla went from $280 to $140, but never sold any.

LinkedIn, a crappy website, was recently purchased by Microsoft for $30 billion. That's about how much Tesla's market capitalization was 2 months ago.

Take a look at the all of the industries that will be impacted by the convergence of self driving cars, electric cars, and ride sharing.

The global parking industry alone, is a $100 billion dollar industry. Other impacted industries include oil, traditional auto, car insurance, auto repair/servicing/maintenance, auto dealers, etc.

Batteries are getting cheaper than anyone ever expected at this point. Solar recently became more competitive for electricity generation than fossil fuels.

The dam is about to burst.

I happen to agree with the author simply based on the tight IAM integration between all AWS products. Working with GCP and manually processing OAuth2.0 tokens (three legged oauth, 2 legged oath, JSON web tokens, callbacks, etc.) with callbacks, signing/storing/expiring certificates is such a nightmare from an integrations perspective. IAM solves all of these problems. IAM alone is reason to go all in with AWS.

I call bullshit on you calling bullshit on every point of this comment.

> How many 'best practices' do you need?

Actually, there should only be one way to do something in a framework. While not a framework, think about the Go language. Go is a very strict, almost paternal language that 'enforces' best practices in the language itself by giving you only one way to do something. Angular, on the other hand, provides numerous ways to create a service. Because of this confusion, the Angular team provides best practices. It's like saying, 'we screwed up in designing this thing, so you have to read all the documentation to find out the subtle differences in all this bullshit.' It's not the lack of best practices that concerns me, it's the abundance of them that gets shipped with a bloated framework that wasn't designed well.

>Every large release?I seriously doubt it.

Think of all the pain involved in removing all of the digest cycle code when switching from Angular 1.4 to Angular 2.0.

> No they don't, maybe a small differences and what do you mean with 'templating'? It's not Angular.

Seriously? There are no small differences between Django templates, Soy templates (client and server side), and Angular templates to name a few. They are all very different yet they do essentially the same thing. At least Soy templates can be used outside of a framework (with either JS or Java).