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.
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.
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Check which file is giving the error, it’s probably being thrown in an included library, not your code.
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.
Just read the whole stack trace till you find a familiar file
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.
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