<story><title>Reddit&apos;s photo albums broke due to Integer overflow of Signed Int32</title><url>https://old.reddit.com/r/shittychangelog/comments/zl5gaz/here_at_reddit_we_believe_everything_is_better_in/</url></story><parent_chain><item><author>kristopolous</author><text>Thinking &amp;quot;if that ever gets anywhere close to a problem we&amp;#x27;ll have vast resources and plenty of time to fix it&amp;quot; and then, I&amp;#x27;m guessing, that person left a few months later and nobody owned that part of the code because it worked.&lt;p&gt;Then 10 or so years went by...&lt;p&gt;Whenever I write code like that which may break in say, 5 years, I&amp;#x27;ll sign it in the comments and put my personal email and phone number inviting future people to call me and I&amp;#x27;ll fix it for free (cause I take responsibilities for my code pretty seriously). Nobody has ever taken me up on it though...</text></item><item><author>fdgsdfogijq</author><text>Someone probably joked they would never reach that scale when they wrote that code</text></item><item><author>Rebles</author><text>Two days ago, Reddit ids have finally incremented passed the 2,147,483,647, or the maximum range of a signed int32. It seems one of Reddit&amp;#x27;s subsystems, the one that serves its photo albums broke due to the integer overflow.</text></item></parent_chain><comment><author>monsieurbanana</author><text>To people reading this: please never ever do that, unless it was agreed upon with your client&amp;#x2F;employer beforehand (and compensated accordingly).&lt;p&gt;If you know the code may break in 5 years, why don&amp;#x27;t you fix it now? Because your employer doesn&amp;#x27;t want to pay you to do that (probably for good reason, surely there&amp;#x27;s higher priorities).&lt;p&gt;Then why would you do it for free years later?</text></comment>
<story><title>Reddit&apos;s photo albums broke due to Integer overflow of Signed Int32</title><url>https://old.reddit.com/r/shittychangelog/comments/zl5gaz/here_at_reddit_we_believe_everything_is_better_in/</url></story><parent_chain><item><author>kristopolous</author><text>Thinking &amp;quot;if that ever gets anywhere close to a problem we&amp;#x27;ll have vast resources and plenty of time to fix it&amp;quot; and then, I&amp;#x27;m guessing, that person left a few months later and nobody owned that part of the code because it worked.&lt;p&gt;Then 10 or so years went by...&lt;p&gt;Whenever I write code like that which may break in say, 5 years, I&amp;#x27;ll sign it in the comments and put my personal email and phone number inviting future people to call me and I&amp;#x27;ll fix it for free (cause I take responsibilities for my code pretty seriously). Nobody has ever taken me up on it though...</text></item><item><author>fdgsdfogijq</author><text>Someone probably joked they would never reach that scale when they wrote that code</text></item><item><author>Rebles</author><text>Two days ago, Reddit ids have finally incremented passed the 2,147,483,647, or the maximum range of a signed int32. It seems one of Reddit&amp;#x27;s subsystems, the one that serves its photo albums broke due to the integer overflow.</text></item></parent_chain><comment><author>jacobr1</author><text>And they weren&amp;#x27;t even wrong! The challenge is addressing the tech-debt, not the choice to incur it.</text></comment>