this post was submitted on 14 Oct 2023
1066 points (97.0% liked)

Programmer Humor

32000 readers
1744 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 34 points 11 months ago (4 children)

Check which file is giving the error, it's probably being thrown in an included library, not your code.

[–] [email protected] 26 points 11 months ago (3 children)

Yeah, but that's some bullshit. I want to know what line in my file is causing the error.

And they know! They know what line in your file caused the error! They know the value of all the variables when the error hit. But do they show that? Fuck no.

[–] [email protected] 11 points 11 months ago (1 children)

Just read the whole stack trace till you find a familiar file

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (1 children)

No offense, but I know how to read a stack trace, and yes locate a familiar file - if you're lucky enough to have one listed therein.

My point is, there is no excuse for them being so terrible except that they've always been that way.

The important information should be brief and at the top. This is design 101. The same ideas that have driven newspaper articles and websites for as long as the two have been a thing.

You put the important stuff in big letters at the top, and the rest, if you need it, is beneath the fold.

Edit: just to drive the point home: I'm sure it's not the packages I've downloaded that are causing the error, I am positive it is my code, so show me where my code had a mistake first. Then you can show me the horrible "wall of text" that is the stack trace so I can understand it better later, but 99% of the time, just seeing the line that caused the error is enough to know what the problem is.

[–] [email protected] 1 points 11 months ago

It's a fair point, it would help a lot, I can see a drawback when the problem is incompatibility between libs or errors inside the lib but it could be solved with a show more option.

I like your ideia, would love to see how it would work

load more comments (1 replies)
load more comments (1 replies)