TLDR: retry only if the error is owned by the immediate next hop (assuming you can determine ownership).
The engineering is sound, but the article misses a important connection to queueing theory which shows in much simpler terms how retries can increase the instability of a system already under stress.
The article is ridden with misconception. Have you guys ever heard of the CAP theorem ?
Disturbed system suck let's implement a non distributed one. The title is also misleading: Postgres transactions are not distributed.
Practically speaking, doesn't using force while preaching democracy just ruin the concept for everyone? If we accept that 'might makes right' in international affairs, we create a world where power—not rights—governs every interaction and where democracy and human rights while they may have tangible reality in some "islands" become propaganda used to gain higher moral ground.
The author of the comment I replied to seems to find it perfectly okay for "might is right" to be the norm. I pointed out that if we believe that this way of thinking is okay at the international politics level then the corollary is that democracy and human right must be a farce. Don't be mistaken, what we see happening at the level of world affairs will trickle down to everyday life. At the world stage, this wicked way of thinking leads to genocides being normalized. At the societal level it leads to societies with no morals. Might is right at every level.
The use of LLMs in software does not stop at code generation. With function calling, the prompt becomes the program and the LLMs acts as an intelligent interpreter/runtime that excutes complex business logic using primitives (the functions) they have access to (MCP) and that's the real paradigm shift for software engineering.
This law is specific to situations of imminent or actual physical harm. Also notice the way the law is formulated: non-assistance (negative) and not a an explicit duty to assist (positive).
People in tech keep complaining about daily standup don't know that is a common practice in pretty much every line of work. It's just a team synchronisation moment.
No github link, high performance claim with 0 numbers. No technical details. 0 interesting link to learn more. But hey a key people page is there so that's ok.
"We’re improving how we communicate future pricing changes" like clearly and explicitly stating what your customers are paying for ? What kind of BS is this ?
Developer experience is awful. Variable names starting with $, heavy object orientism that seems like an after thought, tooling ecosystem is subpar, standard library is a joke, etc
It’s a pile of crap and that’s my opinion
From php.net home page: « PHP 8.2 is a major update of the PHP language.It contains many new features, including readonly classes, null, false, and true as stand-alone types,… »
That says all for me. Doesn’t matter if it powers half the web. It’s an awful programming language.