ティージェーグレェ on Nostr: Glad to read you made a recovery and wow, your wife's response was pretty charming ...
Glad to read you made a recovery and wow, your wife's response was pretty charming too!
This horrified me:
"the production apps would freeze if Sentry didn’t respond. It had been implemented in a blocking way, with a timeout of 300 seconds."
I can't even begin to imagine making a monitoring system blocking. I hope that dev realized how he single-handedly torpedoed the entire project with that idiocy. Though I get the impression since others humored him, it's doubtful he ever realized the error of his ways.
Monitoring and logging can be useful when diagnosing problems, sure; though that's a best case scenario. More often than not such things are a waste of resources entirely and rarely ever looked at if things are going well.
If this kind of dev were to go into a brick and mortar business and claim: that the business couldn't sell something at a register because the building security cameras had been non responsive for the last 5 minutes. Maybe it would help less technical people to understand what a terrible business decision that would be? Or how such a choice would very likely ultimately lead to the demise of any potential profits by focusing on the wrong priorities?
I don't even want to think about how expensive that cloud bill must have been. Then again, as a teenager after I finally got a modem functioning, my first phone bill was so expensive that my parents' confiscated my modem! I learned how to phreak after that and they never saw a phone bill with any toll charges again after that.
My first modem was 1200 baud.
I kind of get the impression that dev never had to deal with constraints or parents like mine. ;)
Sure, I've learned many lessons the "hard" way, but at least I learned them?
This horrified me:
"the production apps would freeze if Sentry didn’t respond. It had been implemented in a blocking way, with a timeout of 300 seconds."
I can't even begin to imagine making a monitoring system blocking. I hope that dev realized how he single-handedly torpedoed the entire project with that idiocy. Though I get the impression since others humored him, it's doubtful he ever realized the error of his ways.
Monitoring and logging can be useful when diagnosing problems, sure; though that's a best case scenario. More often than not such things are a waste of resources entirely and rarely ever looked at if things are going well.
If this kind of dev were to go into a brick and mortar business and claim: that the business couldn't sell something at a register because the building security cameras had been non responsive for the last 5 minutes. Maybe it would help less technical people to understand what a terrible business decision that would be? Or how such a choice would very likely ultimately lead to the demise of any potential profits by focusing on the wrong priorities?
I don't even want to think about how expensive that cloud bill must have been. Then again, as a teenager after I finally got a modem functioning, my first phone bill was so expensive that my parents' confiscated my modem! I learned how to phreak after that and they never saw a phone bill with any toll charges again after that.
My first modem was 1200 baud.
I kind of get the impression that dev never had to deal with constraints or parents like mine. ;)
Sure, I've learned many lessons the "hard" way, but at least I learned them?