sda(programming.dev)

posted 1 month ago

fool@programming.dev

programmer_humor@programming.dev

68 commentshide report

Sort:

Hot Top Controversial New Old

You are viewing a single thread.

View all comments View context

[ - ]

skulbuny@sh.itjust.works

24 points

1 month ago

I learned early in my software engineering career these two beautiful rules of debugging:

Read all of the words
Believe them

permalink

report

parent

[ - ]

smeg@feddit.uk

6 points

1 month ago

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!

permalink

report

parent

[ - ]

Trainguyrom@reddthat.com

3 points

1 month ago

Having written some error messages in a godforsaken database frontend, an error message only means that something didn’t work correctly and may or may not correctly indicate what is actually wrong

permalink

report

parent

[ - ]

skulbuny@sh.itjust.works

2 points

1 month ago

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” 😂

permalink

report

parent

[ - ]

Ethan@programming.dev

2 points

1 month ago

I don’t know, have you ever used JavaScript? I’ve run into some really fucking weird bugs. I’ve also spent hours trying to find the source of an error message only to discover the error message was lying and caused by some other error.

permalink

report

parent

[ - ]

ugo@feddit.it

7 points

1 month ago

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

permalink

report

parent