16
Bubbles
197d

So I’m working on a project right and I don’t run it after writing 104 lines of untested code and it doesn’t work.

Which is expected but then I do some stuff and fix that, I get a new error which is great cause I’m getting closer.

Cut to tonight. I’m trying to hunt and kill this bug. And after doing nothing but copying the code to another text file so I can upload that copy and get help.

I decide to run it with a little just print statement in it to make sure it’s definitely broken and I’m not asking online for no reason.

And.. it works.. WHAT???

I uncomment the rest of the function and get rid of the print statement and scream because ITS WORKING!!

I MEAN IT HAS BUGS BUT THEYRE BUGS I CAN FIX AND FOCUS ON AFTER I FREAK OUT ABOUT IT WORKING AFTER ME CHANGING FUCKING NOTHING.

Comments
  • 1
    been there. Sometimes, all you need is a freaking print statement. truthy story
  • 0
    @JhonDoe I guess so
  • 1
    If it's C it can happen that the program may crash because of a printf. It's a symptom of underlying corrupted memory
  • 1
    The print statement might have fixed something.

    As such, you may find you need a dummy print statement that prints nothing.
  • 1
    This post is suspeciously similar to this one https://devrant.com/rants/2022144/...

    Coincident? I think not...
  • 0
    @Chrupiter it’s C#
  • 0
    @MrCSharp holy shit that’s weird
  • 3
    so true, programming can be an esoteric mindfuckey experience sometimes... I wonder if famous programming people have such hair tearing moments like that...
  • 2
    @gtarsia of course they do, no great achievements come without hardships
  • 1
    > programming can be an esoteric

    > mindfuckey experience sometimes...

    Not just that, but you often have to go through that process to make your PC work in the first place, and keep it working.

    Unless you have someone else on hand for that task.
Your Job Suck?
Get a Better Job
Add Comment