gjhr · HackerTrans

Key word being "most". I attended a state funded grammar school in the 2000s.

See: https://en.wikipedia.org/wiki/List_of_grammar_schools_in_Eng...

gjhr

3 年前議論

https://en.wikipedia.org/wiki/Riffle_shuffle_permutation#Per...

Shows that perfect shuffles can return the deck to the original state.

gjhr

4 年前議論

I think the problem here is that they submitted a fabrication. If someone is prepared to do that, I don't think how they drafted the document is really the issue.

gjhr

5 年前議論

Fair use is not a global concept.

gjhr

5 年前議論

I certainly don't adore him, but would probably read a good biography about him _because_ he is such a controversial figure.

gjhr

5 年前議論

Provisioned concurreny does decrease cold starts.

Reserved concurrency both guarantees a portion of your concurrency limit be allocated to a lambda as well as capping concurrency of that lambda to that portion. Reserved concurrency has no cost associated.

Provisioned concurrency keeps a certain number of execution environments warm for your use. Provisioned concurrency costs money.

gjhr

5 年前議論

Yup. In the UK the benefits of owning are clear, but the entrance requirements can be very high.

gjhr

5 年前議論

> When you run Terraform against AWS on the subnets part, it will create (anytime you deploy) the missing subnets

That is one of the core features of Terraform? Detecting and fixing drift is useful.

gjhr

5 年前議論

Hi, thanks for replying. I'll send you a message on Monday when I get back to work to recreate it.

gjhr

5 年前議論

I'd agree with them that the portal is terrible. Multiple times a day I get blank page errors, where the page is completely blank except for a single non-sensical error message in black text.

However their actual services are also pretty terrible. Pretty much everything takes significantly longer to deploy than the AWS couterpart. There are so many preview and deprecated features that it is often hard to judge exactly what feature set you are getting, this is often compounded by the fact that almost everything has multiple SKUs which also change available features. Azure AD RBAC is a bit of a mess, although its conceptually simpler than AWS IAM policies its just a pain to use in practice, and its often slow for changes in permissions to actually reflect. Azure VM disks are annoying to use too, you can't set the size of the OS drive at creation and extra data disks come unformatted. "Grossly incompetent" is probably an overstep though, Azure is very impressive, just not as impressive as its competitors right now.

Having said all that their are a couple places where Azure really shines in my opinion:

* Resource groups (GCP has a similar feature) allow you to more easily keep track of related resources across services. * Price transparency. Many (not all) services tell you up front hourly/monthly costs as you are deploying them through the portal. You don't have to track down a pricing page or calculator yourself. * Azure functions are amazing when using C#/.Net. A huge amount of the regular boilerplate is abstracted away into simple C# annotations so you can get a large % of business logic.

gjhr

5 年前議論

OK but how does Terraform know you are renaming a resource? It is not a daemon always running and watching everything you type. It only gets a snapshot of your code to work from when you run it, it doesn't know what your code was before, just the saved state from your last run and the real state in your cloud provider. The only way it can track the state is through the name which you have provided it, if you change that name it cannot know without inferring something. Maybe it matches up all the attributes in your code and state and infers that a rename has happened. What happens when only 95% of attributes match? What happens when multiple things match (An ec2 instance only requires 2 attributes so this is plausible)?

Example 1:

You have 2 essentially identical EC2 VMs with terraform names vm1 and vm2. You decide these are not good descriptive names so change them to webserver1 and webserver2, before running that change you also realise you only need 1 of the servers so delete webserver2 from your code. Terraform runs a plan and sees there is now only a single VM definition but 2 VMs in state. Neither of the terraform identifiers match the original resources. How does it know which one was renamed and which one to delete?

Example 2:

You use Terraform for IaC and something like Chef for configuration management so your Terraform code exclusively deals with the "hardware". A service is being migrated to a new implementation so you need to delete the old VM and bring up a new one. Both old and new implementation have the same exact hardware requirements. You make the change in your Terraform code, deleting the old resource and creating a new one with the same requirements but a different name, and run a plan. Terraform tells you there's nothing to change because its inferred that you wanted to rename.

gjhr

5 年前議論

  terraform state mv [old name] [new name]

I'd much rather explicitly state when real resources are renamed than have terraform diffing my code and guessing whether I wanted to rename it or I am actually trying to recreate something. I can only imagine the headaches that would happen with a tool trying to track changes to infra as well as changes to code without explicitly tying infra state to version control somehow.

https://www.terraform.io/docs/cli/commands/state/mv.html

gjhr

5 年前議論

Here in the UK lots of people have garages but I'd actually guess its more common to use them for storage than to keep a car in. Everyone I know who has an electric car keeps it on the drive with an outside charging point.

gjhr

5 年前議論

But that wouldn't have helped here. No companies wanted to lay down cable even when they would then get a monopoly on the customers in the town.

gjhr

5 年前議論

34 billion dollars doesn't count as gobs of money?

gjhr

5 年前議論

I am not a Heroku user so cannot assess how this compares to their offering but as someone who spends ~4 hours a day looking at Terraform and the AWS console this does not look "production" quality at all.

* The web app is deployed to a single AWS EC2 instance which cannot be scaled horizontally.

* The web server is deployed from an AMI filter, when a new AMI matches this filter there will be downtime to redeploy the instance entirely.

* There does not seem to be any considerations for patching the web server.

* Everything shares a single security group. Although this is probably fine because you are using managed services for redis and postgres its still weird to allow port 443/22 from anywhere on your database.

I'd be happy to be proven wrong on these points.

There also seems to be quite a bit of assumed knowledge about AWS and Terraform. You mention the free tier a lot, but that only applies for the first year since your AWS sign up. After the free tier is up this infra is going to cost $40+ per month.

gjhr

6 年前議論

At a guess they are probably saying that a human when looking at a picture of a palm would not be able to tell you who it is, unlike a picture of someone that includes their face or body. Seems a bit of a pointless distinction as the Amazon Go stores heavily rely on cameras to track people when in store.

gjhr

6 年前議論

You can also shift right click the background of an explorer window to open a terminal session (powershell or cmd depending on the release I think). If you need a administrator prompt you can do that from explorer's file menu in Windows 10.

gjhr

6 年前議論

A combination of sign 3, 8 and 12 can be awful. The features that are shipped are half-baked, teams always say that they will come back and refactor it but of course never do. Developers start to care less and less about quality because that isn't what gets rewarded. Feature ship rates go up in the short term but in the long term slow down as the spaghetti gets worse and worse.

Good developers either see what is happening and jump ship or just get bored and leave.

gjhr

6 年前議論

The battery performance of old Spartan edge was amazing, great for laptops/tablets. Have they managed to keep that kind of performance with their new chromium version? (I haven't updated yet)

コメント