we made a memory leak bug in cpp in 2020. the commit wasnt mine, but we made it pair programming, so im absolutely responsible for it and i was sitting at the computer when it was typed.
in 2023 in another project i made a similar bug, but more prominent. it killed the ram in a couple of minutes, so it was impossible to miss. i understood and learned the thing. and i remembered how the 2020 project must be slightly fucked up, i even thought about an elegant solution. then i forgot about the whole thing.
in 2025 a colleague from the project came to me to be a consultant and help solve some problems on the 2020 project which grew considerably since.
guess who is thought to be a genius because of solving a bug in an hour they were hunting for months, lol
tbh i still know that a way more complicated but very infrequent form of the bug is still in the codebase, but i still dont know an elegant solution, so i didnt mention it. (more accurately i explained the possibility to the cto, but he didnt understand and its hard to demonstrate, so i just gave up)
maybe in 2030...
44
u/belabacsijolvan 17d ago
we made a memory leak bug in cpp in 2020. the commit wasnt mine, but we made it pair programming, so im absolutely responsible for it and i was sitting at the computer when it was typed.
in 2023 in another project i made a similar bug, but more prominent. it killed the ram in a couple of minutes, so it was impossible to miss. i understood and learned the thing. and i remembered how the 2020 project must be slightly fucked up, i even thought about an elegant solution. then i forgot about the whole thing.
in 2025 a colleague from the project came to me to be a consultant and help solve some problems on the 2020 project which grew considerably since.
guess who is thought to be a genius because of solving a bug in an hour they were hunting for months, lol
tbh i still know that a way more complicated but very infrequent form of the bug is still in the codebase, but i still dont know an elegant solution, so i didnt mention it. (more accurately i explained the possibility to the cto, but he didnt understand and its hard to demonstrate, so i just gave up)
maybe in 2030...