24
biskazz
8y

"Most coders think debugging software is about fixing a mistake, but that's bullshit. Debugging's actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you've secretly known all along. A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. When a bug finally makes itself known, it can be exhilarating, like you just unlocked something. Because, after all, a bug's only purpose, it's only reason for existence is to be a mistake that needs fixing, to help you right a wrong. And what feels better than that? The bug forces the software to adapt, evolve into something new because of it. Work around it or work through it. No matter what, it changes. It becomes something new. The next version. The inevitable upgrade." - Elliot, Mr. Robot

Comments
  • 9
    nah, I still think it's about fixing a mistake
  • 2
    Well, most of the time applications crash when bug occurs, in some cases they do not work properly as in: "holly shit i just lost 749483 dollars because of this soft!".
    Therefore I do not see any software adopting to bug.
    What's more in my opinion bugs do not represent errors in thinking just errors in implementation. Errors in thinking (for example in algorithms) should be called "defects". Hence bugs are incorrect implementation => they are mistakes (unless the bug was made intentionally).
    However I do agree with first part (about debugging) if you just debug to fix the bug and not to understeand it this fix might make your soft even worse.
  • 1
    @g-m-f big 😇
  • 1
    I disagree with that, most of the time bugs are just typos.
    There are times where the bug is a logic flaw, but that's rare and most of the time more dangerous.
  • 1
    @superuser I wouldnt call typos a bug. Can't see how you would be stuck on them for more then a second.

    I think a bug is something like sessions getting lost in a specific browser for an unkown reason. Or an external API not following its documentation breaking your code. When its working as intended.

    Flaws in logic are in my opion mistakes, If your logic is wrong I would call it a mistake, because the code is doing exactly what you ask it to do. But you are asking the wrong things. ;)

    In my work I charge clients for bugs, but not for my mistakes.

    Not sure if my concept of a bug is the correct one.
  • 0
    @superuser I agree that faults in logic are way more dangerous. Especially when they are found days/weeks after implementation.
Add Comment