6
fzammetti
35d

Let's say you're working on some pretty complex JavaScript code, and it's just not working right, nothing you try seems to fix it and you can't figure out what's going on. So, rather than continuing to bang your head against the desk, you decide to do the smart thing and shut down for the day.

You then come back to it the next day, refreshed and ready to do battle with the code! You start by adding a few simple logging statements to see what the hell is going on.

You then run the code and... IT WORKS PERFECTLY?!

You scratch your head for a while before finally realizing that cache didn't get cleared yesterday, so your changes were never executing.

D'oh!

Do you:

(A) Beat yourself up for missing such a stupid and basic thing despite doing this shit for literally over 25 years now, or:

(B) Do a happy dance because you just got a free day and can effectively start the weekend early knowing you accomplished your goal for the week?

(or, I suppose, both, which is kind of where I land)

Comments
  • 1
    Respect for being able to quit and continue the next day. I recently had to move a char from the middle of the string to the beginning of the string (there was bit more complexity involved ofc) in the most performant way possible (no substr etc). Task for five minutes but kept failing. It was obviously not my day but I kept going. It was a hell
  • 1
    Every so often I find myself with a frontend pointing to some remote backend and for some time I keep wondering why I don't see my local changes to the backend. It happens.
  • 1
    @retoor Sometimes the "simplest" of tasks really does turn into "OMFG WHERE'S THE ALTAR I NEED TO SACRIFICE MY FIRSTBORN ON TO GET THIS F'ING THING TO WORK?!?!"

    ...and because we know it's "simple", it makes it not working that much more galling.
  • 1
    @kamen It sure does, unfortunately :(
  • 0
    Do it like most front-end build systems. Add a hash of the file to the file name so it doesn't get cached.
Add Comment