I have read of the Zero One Infinity rule in software design.
Why is it called this? based on the actual behavior of software and its engineers, wouldn't this be better called the Zero One Two Billion One Hundred Forty-Seven Million Four Hundred Eighty-Three Thousand Six Hundred Forty-Eight rule, or perhaps the Zero One Four Billion Two Hundred Ninety-Four Million Nine Hundred Sixty-Seven Thousand Two Hundred Ninety-Six rule?
The point of the rule that there should be no "magic number" for the upper limit. However practically it's hard to achieve this because there'se some limitation of the implementation like width of integer and similar things. The point is when you move from N bit integer to N+K bit integer the software design should handle it naturally - you shouldn't redesign everything just because of such change. Integer representation limits should not be "magic numbers" here.
Because it's just guidance that suggests artificially limiting the number of instances of an entity is silly. One can easily justify ensuring that zero of a certain thing exist (i.e. yellow elephants). One can also justify having just one of a thing (i.e. one wife, or husband). However, past this limit, it becomes harder to say "Well, we'll only allow 5 Foos" - the limits are often (but not always), relatively arbitrary - someone will always want 6, or 15 etc.
Because it's just a rule of thumb, designed for humans, the upper limit of infinity is interpreted as "As many as you like". Fixing it at a given number defeats the point of the rule.