Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.