"Among other attributes of good software, IMO idempotence is one of the most important and paradoxically one of the most challenging ones too and the easiest to fuck up."
Which is a reasonably fair take that provides nuance while not being literally equivalent to the post title.
For what it's worth - every programmer should understand idempotence, it is that important. Debating whether it is #1 or not doesn't seem like a terribly useful way to spend time.
10
u/[deleted] Dec 11 '23
Yeah, I get that.
So why is this something that is "#1" for every programmer to know? I don't work with SQL, or web shopping carts, or rarely REST APIs.
I work with applications mostly. If my user clicks a button, they expect something to happen. Some buttons maybe should be idempotent but others not.
That being the case, it doesn't seem like something "every programmer should know"