552 karma · joined June 3, 2019
What he meant is that is an unexpected condition, that should have never happened, but that did, so it needs to be fixed.
> How is someone supposed to even notice a random error log?
Logs should be monitored.
> At the places that I've worked, trying to make alerting be triggered on only logs was always quite brittle, it's just not best practice.
Because the logs sucked. It not common practice, it should be best practice.
> Throw an exception / exit the program if it's something that actually needs fixing!
I understand the sentiment, but some programs cannot/should not exit. Or you have an error in a subsystem that should not bring down everything.
I completely agree with the approach of the author, but also understand that good logging discipline is rare. I worked in many places where logs sucked, they just dumped stuff, and had to restructure them.
> Russia has vast natural resources and enough buyers
Not saying that it's not what has kept them standing until now, but the buyers make the price in this case. So who knows what the price could become in the future.
> Will they try to buy it out and bring a (even more) fascist autocratic regime there? Probably yes.
Are you still talking about Russia with their monopoly currency? "Try" as in one probability over one billion to succeed and be disposed of a few days later. This ability to influence foreign countries effectively and not in clownish ways is a nice story for kids.
If I had a dollar for every time a serious vulnerability that started like this was discovered in the last 30 years...
What does he mean, isn't this what OpenAI just did, I'm confused guys
Eager to do what? If it sucks it sucks, but that's a very childish way to frame it, no one did anything on purpose or out of spite. That kind of silliness hurts the image of the project. But bad translation I suppose.
Implementations varies, no one forces the third party to use message types 100% as intended.
Yes, I also put Redis in that list. You can cache and serve data structure in many other ways, for example replicate the individual features you need in you application instead of going the lazy route and another service to the mix. And don't get me started on Kafka... money thrown in the drain when a stupid grpc/whatever service would do.
Part of being an engineer is also selecting the minimum amount of components for your architecture and not being afraid of implementing something on your own if you only need 1 of 100s features that an existing product require.
But I think they already clarified how much they care about people doing translations since they defaulted to the robo-translation. Which to me is complete nonsense considering how superior the human translations must be. As a human with a brain, I would have just translated automatically the missing pages leaving to them the option of replacing/fixing them. Also they should have been thanked many times for all their hard work.