▲ 820 ▼ That Nim Flashbacks (sh.itjust.works) submitted 2 years ago by pastermil@sh.itjust.works to c/programmer_humor@programming.dev 56 comments fedilink hide all child comments
[–] lowleveldata@programming.dev 54 points 2 years ago (2 children) I like recursive functions tho permalink fedilink source hideshow 4 child comments replies: [–] pastermil@sh.itjust.works [S] 37 points 2 years ago (2 children) Yet I have not met a CS grad without a trauma. permalink fedilink source parent hideshow 4 child comments replies: [–] Lemminary@lemmy.world 14 points 2 years ago I've had 7 traumas this week and counting *rocks back and forth* permalink fedilink source parent [–] xmunk@sh.itjust.works 12 points 2 years ago (2 children) I have a production bug... it only happens on Saturdays ever our ops folks have no idea - this can be replicated on a test server that gets no traffic. Saturday why! permalink fedilink source parent hideshow 4 child comments replies: [–] sukhmel@programming.dev 5 points 2 years ago (1 child) If we reject the theory that it could be someone's elaborate revenge, Saturday may be the first day of the week that may become workday or non-workday because of incorrect assumption about the first day of the week. If everywhere but one place in your software the day numeration is correct it would be a hard bug to spot. Also, if it is in Java, I vaguely remember there being a lot of ways to express weekday, so a lot of ways to shoot off your foot (solely on Saturday) permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) For bonus points, this failure is in a cron job that sends out recently queued messages. It runs once every ten minutes - last weekend we had 12 failures: four were in a cluster on their own, one was in a run of two, and six were in a single continuous run. Please note that this server is unused by our business so no messages ever get naturally queued. Every day we sync the live production server to this server at about 9 PM - assuming an employee was queuing up a message before the snapshot is taken there might be a number of unsent messages in the snapshot - those messages will all be sent by the first cron job after the sync. It is a wonderfully awful problem that has me wanting to pull out my luscious locks. permalink fedilink source parent hideshow 2 child comments replies: [–] sukhmel@programming.dev 4 points 2 years ago (1 child) I wish you luck. Also, maybe you could get someone else to get a fresh view of an issue permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent [–] CanadaPlus@lemmy.sdf.org 3 points 2 years ago* Please tell me it doesn't still happen when you emulate a different day of the week. Or is that non-trivial to even do because of technical debt? Either way, RIP weekends. permalink fedilink source parent [–] Blue_Morpho@lemmy.world -1 points 2 years ago I've always hated recursion. It's always seemed like a cutesy programming trick that's not reliable in all conditions. You could blow the stack in an edge case that you didn't think of. So it should never be a standard pattern. It's only good if you need to rewrite something for optimization and recursion is appropriate. But in many cases recursion is slower. "Look at what I can do in 5 lines of code!" is for programming contests, not for anything important. permalink fedilink source parent
[–] pastermil@sh.itjust.works [S] 37 points 2 years ago (2 children) Yet I have not met a CS grad without a trauma. permalink fedilink source parent hideshow 4 child comments replies: [–] Lemminary@lemmy.world 14 points 2 years ago I've had 7 traumas this week and counting *rocks back and forth* permalink fedilink source parent [–] xmunk@sh.itjust.works 12 points 2 years ago (2 children) I have a production bug... it only happens on Saturdays ever our ops folks have no idea - this can be replicated on a test server that gets no traffic. Saturday why! permalink fedilink source parent hideshow 4 child comments replies: [–] sukhmel@programming.dev 5 points 2 years ago (1 child) If we reject the theory that it could be someone's elaborate revenge, Saturday may be the first day of the week that may become workday or non-workday because of incorrect assumption about the first day of the week. If everywhere but one place in your software the day numeration is correct it would be a hard bug to spot. Also, if it is in Java, I vaguely remember there being a lot of ways to express weekday, so a lot of ways to shoot off your foot (solely on Saturday) permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) For bonus points, this failure is in a cron job that sends out recently queued messages. It runs once every ten minutes - last weekend we had 12 failures: four were in a cluster on their own, one was in a run of two, and six were in a single continuous run. Please note that this server is unused by our business so no messages ever get naturally queued. Every day we sync the live production server to this server at about 9 PM - assuming an employee was queuing up a message before the snapshot is taken there might be a number of unsent messages in the snapshot - those messages will all be sent by the first cron job after the sync. It is a wonderfully awful problem that has me wanting to pull out my luscious locks. permalink fedilink source parent hideshow 2 child comments replies: [–] sukhmel@programming.dev 4 points 2 years ago (1 child) I wish you luck. Also, maybe you could get someone else to get a fresh view of an issue permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent [–] CanadaPlus@lemmy.sdf.org 3 points 2 years ago* Please tell me it doesn't still happen when you emulate a different day of the week. Or is that non-trivial to even do because of technical debt? Either way, RIP weekends. permalink fedilink source parent
[–] Lemminary@lemmy.world 14 points 2 years ago I've had 7 traumas this week and counting *rocks back and forth* permalink fedilink source parent
[–] xmunk@sh.itjust.works 12 points 2 years ago (2 children) I have a production bug... it only happens on Saturdays ever our ops folks have no idea - this can be replicated on a test server that gets no traffic. Saturday why! permalink fedilink source parent hideshow 4 child comments replies: [–] sukhmel@programming.dev 5 points 2 years ago (1 child) If we reject the theory that it could be someone's elaborate revenge, Saturday may be the first day of the week that may become workday or non-workday because of incorrect assumption about the first day of the week. If everywhere but one place in your software the day numeration is correct it would be a hard bug to spot. Also, if it is in Java, I vaguely remember there being a lot of ways to express weekday, so a lot of ways to shoot off your foot (solely on Saturday) permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) For bonus points, this failure is in a cron job that sends out recently queued messages. It runs once every ten minutes - last weekend we had 12 failures: four were in a cluster on their own, one was in a run of two, and six were in a single continuous run. Please note that this server is unused by our business so no messages ever get naturally queued. Every day we sync the live production server to this server at about 9 PM - assuming an employee was queuing up a message before the snapshot is taken there might be a number of unsent messages in the snapshot - those messages will all be sent by the first cron job after the sync. It is a wonderfully awful problem that has me wanting to pull out my luscious locks. permalink fedilink source parent hideshow 2 child comments replies: [–] sukhmel@programming.dev 4 points 2 years ago (1 child) I wish you luck. Also, maybe you could get someone else to get a fresh view of an issue permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent [–] CanadaPlus@lemmy.sdf.org 3 points 2 years ago* Please tell me it doesn't still happen when you emulate a different day of the week. Or is that non-trivial to even do because of technical debt? Either way, RIP weekends. permalink fedilink source parent
[–] sukhmel@programming.dev 5 points 2 years ago (1 child) If we reject the theory that it could be someone's elaborate revenge, Saturday may be the first day of the week that may become workday or non-workday because of incorrect assumption about the first day of the week. If everywhere but one place in your software the day numeration is correct it would be a hard bug to spot. Also, if it is in Java, I vaguely remember there being a lot of ways to express weekday, so a lot of ways to shoot off your foot (solely on Saturday) permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) For bonus points, this failure is in a cron job that sends out recently queued messages. It runs once every ten minutes - last weekend we had 12 failures: four were in a cluster on their own, one was in a run of two, and six were in a single continuous run. Please note that this server is unused by our business so no messages ever get naturally queued. Every day we sync the live production server to this server at about 9 PM - assuming an employee was queuing up a message before the snapshot is taken there might be a number of unsent messages in the snapshot - those messages will all be sent by the first cron job after the sync. It is a wonderfully awful problem that has me wanting to pull out my luscious locks. permalink fedilink source parent hideshow 2 child comments replies: [–] sukhmel@programming.dev 4 points 2 years ago (1 child) I wish you luck. Also, maybe you could get someone else to get a fresh view of an issue permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent
[–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) For bonus points, this failure is in a cron job that sends out recently queued messages. It runs once every ten minutes - last weekend we had 12 failures: four were in a cluster on their own, one was in a run of two, and six were in a single continuous run. Please note that this server is unused by our business so no messages ever get naturally queued. Every day we sync the live production server to this server at about 9 PM - assuming an employee was queuing up a message before the snapshot is taken there might be a number of unsent messages in the snapshot - those messages will all be sent by the first cron job after the sync. It is a wonderfully awful problem that has me wanting to pull out my luscious locks. permalink fedilink source parent hideshow 2 child comments replies: [–] sukhmel@programming.dev 4 points 2 years ago (1 child) I wish you luck. Also, maybe you could get someone else to get a fresh view of an issue permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent
[–] sukhmel@programming.dev 4 points 2 years ago (1 child) I wish you luck. Also, maybe you could get someone else to get a fresh view of an issue permalink fedilink source parent hideshow 2 child comments replies: [–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent
[–] xmunk@sh.itjust.works 4 points 2 years ago (1 child) Yup, luck is appreciated and I'm trying to get more eyes but unfortunately I'm a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it. permalink fedilink source parent hideshow 2 child comments replies: [–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent
[–] Sacreblew@lemmy.ca 3 points 2 years ago Lots of logging to triangulate when it fails and what variables it has at the time. permalink fedilink source parent
[–] CanadaPlus@lemmy.sdf.org 3 points 2 years ago* Please tell me it doesn't still happen when you emulate a different day of the week. Or is that non-trivial to even do because of technical debt? Either way, RIP weekends. permalink fedilink source parent
[–] Blue_Morpho@lemmy.world -1 points 2 years ago I've always hated recursion. It's always seemed like a cutesy programming trick that's not reliable in all conditions. You could blow the stack in an edge case that you didn't think of. So it should never be a standard pattern. It's only good if you need to rewrite something for optimization and recursion is appropriate. But in many cases recursion is slower. "Look at what I can do in 5 lines of code!" is for programming contests, not for anything important. permalink fedilink source parent