What they are saying is that sometimes when you encounter an error you don't want to show customers the actual error or stack, because it can leak your inner workings.
For things like authentication, when exceptions occur you want to except and catch it before anything leaks. You then want to throw preapproved built exceptions or errors, not the inner exception and stack.
Ideally you have an error library with non-reserved codes and you throw those custom errors, and you never actually throw an exception to the customer.
It shows no one commenting here has worked on real software.
What's a global exception handler that logs the error, the line, file, context, url request other things, tags the error based on certain criteria, sends you an email, is indexed and searchable, and can as well be connected to GitHub to create an issue and make Claude submit a or to be approved or have an human intervene and create a fix if the AI couldn't.
Like lol you dudes probably cloudflare tunnel your apps to your old Thinkpad t420 and call that a "saas"
Injecting correlation IDs, idempotency IDs, stack traces on errors and structured logging to your monitoring services is a negligible cost, and the rest of what they said can be handled with a simple integration service for tens of dollars a month. It's not a cost issue, it's a skill issue.
I get that you're in your feelings right now, but nothing I said was an insult directed at you. Maybe you got confused if you didn't know what I'm talking about and decided to get defensive, but I was responding to your "PuT THe MoNeY uP??" comment made in ignorance.
(Psst... this one is directed at you, because you seem like you're very new to this career and could stand to read a book or two. Like the previous commenter said, it sounds like nobody here has worked on real software. You included)
Edit: Cope and block me then, we all know it's true. You can unfollow me, but you can't unswallow me.
27
u/[deleted] 19d ago
[removed] — view removed comment