I can absolutely guarantee that you are not the only person to have spent quality time getting to know the intimate backwaters of a codebase tracking down a bug that you introduced whilst tracking down a bug.
Source: I’ve been writing software for over 40 years.
I call that Tuesday.
A colleague is currently checking why the testing environment was uploading files to the production environment. A number of employees’ photos now show Goku
Your bug sounds pretty strong, can I fight it?
Today I spent multiple hours trying to debug a timezone issue in a codebase. The timezone I was testing with was
Etc/GMT+4, which I had assumed was four hours ahead of GMT. Turns out, it’s actually 4 hours behind GMT 🤦♂️I cannot express how much I hate that timezones aren’t flipped.
12:00+02:00should be equal to14:00+00:00like a math equation!
I’m in this picture and I don’t like it. Yesterday I was trying to debug my reverse proxy setup for a new app and why it wouldn’t work.
Well, if you configure it to route shinyNewApp.example.com to your app, but then always access sihnyNewApp.example.com with your browser…
I was reading Crafting Interpreters. After adding function calls and stack frames, i tested my implementation with the Fibonacci script at the end of the chapter
I spent about 2 hours debugging my call stack, and even tested the script in Python
Only to realize that Fib(3) is indeed 2
Jiminy Cricket, imagine not being able to tell the difference between an error code and an image of an error code, and imagine subsequently, for some reason, not immediately inspecting the HTTP request and response. Sounds like a very real #programming #devops problem.
Sometimes you lose the forest for the trees
Sometimes you forget to verify if your assumptions are true
