https://chatgpt.com/share/6747c7d9-47e8-8007-a174-f977ef82f5...
8,467 karma · joined January 12, 2013
https://chatgpt.com/share/6747c7d9-47e8-8007-a174-f977ef82f5...
(1 + 2) × 3 + 4 × 5 + (6 × 7 + 8) × 9 = 479
Source: https://chatgpt.com/share/6747c32e-1e60-8007-9361-26305101ce...This is especially useful in scenarios where multiple users or processes are working on the same data, as it helps maintain consistency and avoids accidental overwrites.
This is using the same mechanism as HTTP's `If-None-Match` header so it's easier to implement/learn
Edit: oh it’s only in one AZ
The Git team should really invest in tooling for very large repos. Our repo is around 10M files and 100M lines of code and no amount of hacks on top of Git (cache, sparse checkout etc etc) is not really solving the core problem.
Meta and Google have really solved this problem internally but there is no real open source solution that works for everyone out there.
I know there are solutions for this, but in the real world I have not seen it properly implemented.
It used to be that the frontend was very fragile. XVFB, Selenium, ChromeDriver, etc., used to be the cause of pain, but recently the frontend frameworks and browser automation have been solid. Headless Chrome hardly lets us down.
The biggest pain in e2e testing is that tests fail for reasons that are hard to understand and debug. This is a very, very difficult thing to automate and requires AGI-level intelligence to really build a system that can go read the logs of some random service deep in our service mesh to understand why an e2e test fails. When an e2e test flakes, in a lot of cases we ignore it. I have been in other orgs where this is the case too. I wish there was a system that would follow up and generate a report that says, “This e2e test failed because service XYZ had a null pointer exception in this line,” but that doesn’t exist today. In most of the companies I’ve been at, we had complex enough infra that the error message never makes it to the frontend so we can see it in the logs. OpenTelemetry and other tools are promising, but again, I’ve never seen good enough infra that puts that all together.
Writing tests is not a pain point worth buying a solution for, in my case.
My 2c. Hopefully it’s helpful and not too cynical.
Did I miss something? Did they have to make changes to the model for this?
The analogy to noise-cancelling headphones is helpful but in that case we clearly know which is signal and which is noise. Here, if we knew why would we even bother to the noise-cancelling work?
Do path parameters get to have / in their values?
Let’s say you have a link shortener service and want to allow users to define shortcuts like /mypath/:rest where rest is appended to example.com/
Now you’re in a very interesting position when it comes to resolving URLs.
Curious to hear folks with experience in this
Stackoverflow makes the slug completely optional but you have the choice of only accepting foo and bar in your example
function add(a,b) {
return 4
}
Passes the testThe technology is there, as demonstrated by OpenAI's ChatGPT Voice Mode. With the resources and talent that Amazon possesses, they should at least be able to demo something similar. It's just that the Alexa organization is a mess, which prevents it from happening.