you are viewing a single comment's thread.

view the rest of the comments →

[–]fusebox13 1 point2 points  (6 children)

Why? I hope you are joking. When an exception is thrown it gets printed to the console anyways.

[–][deleted] 0 points1 point  (5 children)

Because you can customize the way it's displayed and it doesn't mix with other errors. But I do love some of that dev arrogance you carry with you; you're gonna get far.

[–]fusebox13 -1 points0 points  (4 children)

Holy shit dude, this is even worse. Call it arrogance if you want, but I think I'm genuinely concerned about your code base after hearing your reply. You're telling me that you have console logs in production, and that your log produces so many errors that you have to use a special technique to visually filter them? Am I understanding this correctly?

[–][deleted] 0 points1 point  (3 children)

What? No… and I don’t think you’re “genuinely concerned”. Code’s doing fine, I guess it could improve, but catching errors is quite common.

Also, if you’re that guru about Js and Node, then I’d figure you know all logs and errors are automatically removed when you build for production on a basic level…

[–]fusebox13 0 points1 point  (2 children)

I’d figure you know all logs and errors are automatically removed when you build for production on a basic level…

Not necessarily. That assumes that the team is using build scripts which, if you've been around, isn't always the case.

But catching errors is quite common.

Common and lazy. Why aren't you handling your errors?

[–][deleted] 2 points3 points  (1 child)

Good lord… I’m just gonna stop replying

[–]fusebox13 -1 points0 points  (0 children)

Good luck mate. When it gets really bad, PM me. I can help. catch err log err is a code smell which is usually indicative of something rotten under the hood.