fool@programming.dev to Programmer Humor@programming.dev · 21 hours agoof=/dev/sdaprogramming.devimagemessage-square47fedilinkarrow-up1446arrow-down110
arrow-up1436arrow-down1imageof=/dev/sdaprogramming.devfool@programming.dev to Programmer Humor@programming.dev · 21 hours agomessage-square47fedilink
minus-squareskulbuny@sh.itjust.workslinkfedilinkEnglisharrow-up21·18 hours agoI learned early in my software engineering career these two beautiful rules of debugging: Read all of the words Believe them
minus-squaresmeg@feddit.uklinkfedilinkEnglisharrow-up2·2 hours agoAddendum to 2: never believe that what they say is relevant to what’s actually happening here. You have a lot of faith that the people writing error messages knew what they were doing!
minus-squareskulbuny@sh.itjust.workslinkfedilinkEnglisharrow-up2·edit-22 hours agoI mean, if the error says “variable foo is not defined” I don’t think it’s wise to go “I’m pretty sure it’s defined, the compiler is just wrong” 😂
minus-squareugo@feddit.itlinkfedilinkarrow-up6·14 hours agoUntil you write a compiler error in some deeply templated C++ code, in which case just reading every word takes all day /s but not too much
minus-squareelvith@feddit.orglinkfedilinkarrow-up9·edit-217 hours agoUnless you were the one writing the program and its error messages - then check, that you didn’t mess up there…
I learned early in my software engineering career these two beautiful rules of debugging:
Addendum to 2: never believe that what they say is relevant to what’s actually happening here. You have a lot of faith that the people writing error messages knew what they were doing!
I mean, if the error says “variable foo is not defined” I don’t think it’s wise to go “I’m pretty sure it’s defined, the compiler is just wrong” 😂
Until you write a compiler error in some deeply templated C++ code, in which case just reading every word takes all day
/s but not too much
Unless you were the one writing the program and its error messages - then check, that you didn’t mess up there…