fool@programming.dev to Programmer Humor@programming.dev · 3 months agoof=/dev/sdaprogramming.devexternal-linkmessage-square49fedilinkarrow-up1352arrow-down111
arrow-up1341arrow-down1external-linkof=/dev/sdaprogramming.devfool@programming.dev to Programmer Humor@programming.dev · 3 months agomessage-square49fedilink
minus-squareskulbuny@sh.itjust.workslinkfedilinkEnglisharrow-up18·3 months agoI learned early in my software engineering career these two beautiful rules of debugging: Read all of the words Believe them
minus-squareElvith Ma'for@feddit.orglinkfedilinkarrow-up7·edit-23 months agoUnless you were the one writing the program and its error messages - then check, that you didn’t mess up there…
minus-squareugo@feddit.itlinkfedilinkarrow-up4·3 months 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-squaresmeg@feddit.uklinkfedilinkEnglisharrow-up1·3 months 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!
I learned early in my software engineering career these two beautiful rules of debugging:
Unless you were the one writing the program and its error messages - then check, that you didn’t mess up there…
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
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!