Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Elyz632376dForgive me father for I have sinned and done this in many a uni-project where proper exception handling wasn't a success criteria 😔
TangChr505976dReal developers use try-catch instead of if-else
deviloper250176dthat's how I survived in the last 5 years.
I used to write a log or send an email with stack trace, so I was able to fix production bugs in a very reactive way.
After 100 customers, I dropped emails and logs, so now the application run flawlessly and I sleep better.
When the customer finds a bug, if it's important enough, he will call support....
deviloper250176d@Voxera I believe that. However in my business, Directors buy our application and Slave Employees use it. It's enough to take care that bug don't bubble up to Directors. And even then, just make our Director speak with their Director and blame poor slave users.
Hence, my strategy is 100% effective
BluePanda28375dI used to log things in those... then IA decided to listen to Fortify's many complaints about log statements, even in debug mode... Fortify doesn't seem to care if it's empty, so long as it isn't "overly broad". :-/ Yup... definite improvement.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job