My main rule is never to commit code you don’t understand because it’ll get away from you.
I employ a few tricks:
1- I avoid auto-complete and always try to read what it does before committing. When it is doing something I don’t want, I course correct before it continues
2- I ask the LLM questions about the changes it is making and why. I even ask it to make me HTML schema diagrams of the changes.
3- I use my existing expertise. So I am an expert Swift developer, and I use my Swift knowledge to articulate the style of what I want to see in TypeScript, a language I have never worked in professionally.
4- I add the right testing and build infrastructure to put guardrails on its work.
5- I have an extensive library of good code for it to follow.
A friend that used to be high up at Amazon fulfillment told me inventory commingling was the reason he was unwilling to buy anything from Amazon to put in or on his body. Huge indictment for the brand and clearly a bad long-term strategy in the age of fake internet everything.
This will hopefully be a huge improvement for the reduction of fraud on the platform. Hopefully, they give the ability to only buy from verified vendors. This is why only buy CPGs on Walmart.
Hopefully this will really end commingling. I received a pair of bicycle tires as a gift (they bought on Amazon instead of locally) and even though everything looked identical, one tire was somewhat stiffer and weighed 100g more. I wouldn't have really known (at least) one was counterfeit if both had been or i only got one.. really messed up for certain products. Hopefully the flea and tick or worm medicine for my pets is authentic (tractor supply or similar is too far)..
Congrats!! I see this as two great companies joining forces in a crowded space where it is clear the whole is worth more than the sum of their parts. Best of luck on your journey
Definitely has similarities. I think we do not realize how most top websites and services rarely go down anymore, and we use them 100 times more than we did 20 years ago. Building your own networking, compute, storage, CDN, or database solutions to avoid dependencies on AWS or Cloudflare would almost certainly lead to more service downtime than relying on highly sophisticated third parties.
But now, when one of these services breaks, everything on the internet goes down. And it is a lot easier to explain to your director of engineering that the whole internet is down than to say that your custom home-rolled storage system fell over, or whatever esoteric infrastructure failure you may run into doing it yourself.
1. Put a moderate amount of money toward having the world's experts in uptime keep your site performing fast, and accept that occasionally your service goes down at the same time as everyone else.
2. Roll your own service, hire a large number of expensive experts to try to solve these problems yourself, and be responsible for your own outages and failures which will happen eventually and probably more frequently.
If no one is going to die from your service going down, it seems like this is a perfectly reasonable third-party dependency. And if the issue is just your contract's SLA or a financial customer, the saving that comes from using Cloudflare can probably be worked through via negotiations.
I don’t think I like several of his ideas or think he will get most of them passed. In fact I think a few like “freezing the rent” are actively bad
But I’m happy to finally have a politician who lives in and loves New York and is earnestly trying to my the city better. If he tries and fails, it will be better than our other politicians that have stopped trying
Particularly in comparison to Cuomo who by all accounts doesn’t even seem to like the city he campaigned to run. A tiny bit of joy goes a very long way.
Strong agree. I think his policies are absurd but hope that more invested young people who aren’t career politicians can start trying a platform that isn’t party line and resonates with residents.
Its freshwater and has to be freshwater because it goes through pipes and/or is evaporated. Corrosion, scaling and fouling are all issues.
Even if seawater was easy to use and datacenters were near the shore, it would produce very saline brine which would be difficult to safely get rid of.
There was a very large outage back in ~2017 that was caused by DynamoDB going down. Because EC2 stored its list of servers in DynamoDB, EC2 went down too. Because DynamoDB ran its compute on EC2, it was suddenly no longer able to spin up new instances to recover.
It took several days to manually spin up DynamoDB/EC2 instances so that both services could recover slowly together. Since then, there was a big push to remove dependencies between the “tier one” systems (S3, DynamoDB, EC2, etc.) so that one system couldn’t bring down another one. Of course, it’s never foolproof.
> Initially, we were unable to add capacity to the metadata service because it was under such high load, preventing us from successfully making the requisite administrative requests.
It isn't about spinning up ec2 instances or provisioning hardware. It is about logically adding the capacity to the system. The metadata service is a storage service, so adding capacity necessitates data movement. There are a lot of things that need to happen to add capacity while maintaining data correctness and availability (mind at this point, it was still trying to fulfill all requests)
I employ a few tricks:
1- I avoid auto-complete and always try to read what it does before committing. When it is doing something I don’t want, I course correct before it continues
2- I ask the LLM questions about the changes it is making and why. I even ask it to make me HTML schema diagrams of the changes.
3- I use my existing expertise. So I am an expert Swift developer, and I use my Swift knowledge to articulate the style of what I want to see in TypeScript, a language I have never worked in professionally.
4- I add the right testing and build infrastructure to put guardrails on its work.
5- I have an extensive library of good code for it to follow.
reply