Important Breakup Advice:
Make a list of everything you hated about being with them, focus on the bad feelings their behavior gave you.
When you get sad about not being with them refer to the list. It works surprisingly well.
erogenouswarzone
joined 1 year ago
I think it's very cool. Let Reddit have them. We're doing pretty good over here so far. The last thing we need is to be overrun by normies again.
The place I work decided to name all tables in all caps. So now every day I have to decide if I want to be consistent or I want to have an easy life.
Even using absolute best prackies, developers are gonna find a bunch of stuff to complain about.
As a person who victimizes coworkers like this, I apologize. Thank you for pointing it out, and I will stop doing it.
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.
Hey hey. JavaScript is easy. It's when you get into virtual doms that debugging becomes a nightmare.
Can you give us an eli5 on sourcemaps?
It is 2023 my brother in christ! We deserve better error outputs than a stack trace.
- Tell me what line in my file caused the error,
- Tell me the values of the variables involved,
- Then you can have the stack trace.
Why are we pretending like these error messages are acceptable in 2023?!
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.
Also the part where someone else wrote the code 20 years ago, and they haven't worked for the co for 19 years. And now you have to find a bug that makes no sense, with no idea how he even compiled the code. You work on it for 3 months and every day someone's riding your ass about it till they finally say well, let's put it in the backburner.
Nooo. You need the perfect amount of water so it reabsorbs it's own juices. Succulent Cannibalism.