It does if your key is an auto increment or random unique identifier. But if you had a key that is also data, say a "Genre" colum, it starts to make sense that you'd want to cascade updates
I liked gomega and ginkgo when I worked with it. But by virtue of running tests serially, the race detection becomes useless during testing, and I think it's a must have. Has it changed?
I have no idea. I never considered that it would affect using the race detector and it's been so long now I don't know that we cared / ran into this issue so no clue if it has been fixed.
Dumb people exist -just as ugly people do- that already have employment problems. And education can't fix it, because there is only so much they are capable of learning.
As we do away with the easy dumb jobs, we condemn more people to poverty. We surely need to figure something out, specially if we are going to keep raising the bar.
Phone support is a bigger problem from my experience. Exact same setup in my car works flawlessly with some phone models and has any number of issues with others.
I've solved the replaying bit before with a brute approach and AWS Athena. It would ingest all the events from S3, filter the unwanted ones out, and put the rest in SQS ready for consumption. It was definitely expensive though, not something you would run often.
This is definitely a valid approach and it is an expensive path. Athena charges a hefty amount per query if you have a large dataset. In addition, this approach won't work if your data is serialized with something like protobuf.