• palordrolap@fedia.io
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    2 days ago

    Sometimes, when something won’t even compile, I have try to compile it a second time - and get the exact same error message(s) - before my brain will accept there is a problem and perhaps begin to see the cause.

    Somewhere in my head must be a gremlin who says, “No! It is the compiler that is wrong!”

    The same can apply to semantic errors (the code is valid but does not do what it was intended to do) but those take longer to track down. To make the trick work, the debugging output has to be in just the right place in order to print proof of the wrong logic and then do the same on the next run, preferably in under a minute, so that I can begin to see the error.

  • PhobosAnomaly@feddit.uk
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    2 days ago

    “maybe if I hit ‘compile’ really fast, then the bug might not have time to manifest itself this time”

  • danhab99@programming.dev
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    2 days ago

    I work from home in a house next to a highway, I regularly allow myself to scream outloud at the top of my lungs without any consequences. But I got a cat afew months ago and I don’t wanna scare him, then I loose control and scream at my work, and he gets scared, and then I cry and regret letting myself get used to doing that.

  • Beastimus@slrpnk.net
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    2 days ago

    I have had times when closing the application and reopening the project fixes the bug. But only on godot.