4 ms·

Exactly, I've been programming for a long time, almost 13 years since I started working on complex software and that question just makes me draw a blank. There'

Exactly, I've been programming for a long time, almost 13 years since I started working on complex software and that question just makes me draw a blank. There's been bugs in my career but none that have "traumatized" me or been all that complicated to get through. Maybe I just don't put that much emphasis on negative experiences. I don't remember losing poker hands all that accurately either, I just don't care. Also if you've only ever worked in web dev or something easy like that are there even that many really "weird" bugs anymore? Maybe if you work on embedded or low level code bases with lots of race conditions.. those could qualify but if you're doing high level work.. that's rare

teaearlgraycold 4y ago
Working with Rails I learned, after much hair loss, that Class.new is a memory leak. So it can happen in high level languages, too.
ThrustVectoring 4y ago
Web dev still has tons of weird bugs, tend to be in the interactions between multiple frameworks and edge cases in the assumptions they make. Like, I had one issue with intermittent test failures in Ruby on Rails, not reproducible with any fixed seed, and not affecting production. The overall source of it was: 1. We had a table from a third-party API that used their ID as a primary key, I believe stored as a string. 2. Ruby on Rails believed that it should make sure that primary keys aren't a too-large-to-store integer before attempting to save a row. 3. Our test suite would generate fake hexadecimal strings for the primary key for testing purposes for the table. 4. Sometimes, the hexadecimal string would have enough leading 0-9 digits that when Rails coerced it to an integer for their own internal checks, it would exceed the integer limit it thought the table ought to have. I honestly only figured it out by getting lucky.

4 ms·

Exactly, I've been programming for a long time, almost 13 years since I started working on complex software and that question just makes me draw a blank. There'

by jack_pp 4y ago

teaearlgraycold 4y ago
Working with Rails I learned, after much hair loss, that Class.new is a memory leak. So it can happen in high level languages, too.
ThrustVectoring 4y ago
Web dev still has tons of weird bugs, tend to be in the interactions between multiple frameworks and edge cases in the assumptions they make. Like, I had one issue with intermittent test failures in Ruby on Rails, not reproducible with any fixed seed, and not affecting production. The overall source of it was: 1. We had a table from a third-party API that used their ID as a primary key, I believe stored as a string. 2. Ruby on Rails believed that it should make sure that primary keys aren't a too-large-to-store integer before attempting to save a row. 3. Our test suite would generate fake hexadecimal strings for the primary key for testing purposes for the table. 4. Sometimes, the hexadecimal string would have enough leading 0-9 digits that when Rails coerced it to an integer for their own internal checks, it would exceed the integer limit it thought the table ought to have. I honestly only figured it out by getting lucky.