Irony
-
I was hoping (and still am) that this was going to be a 'well, ironically, having made an attempt at writing a HAL in Python, the kiddies have discovered that they can't do it, and have come to me cap in hand to help them' I LIVE for that post, Marc
Garth J Lancaster wrote:
I LIVE for that post, Marc
Actually, what's worse is that one of them said the UI (Javascript/HTML hosted in a CefSharp browser client) was ready for QA, so I volunteered to pre-QA the UI before we sent it over the fence to the "real" *cough* *cough* QA people. An hour later, I had 8 pages of bugs. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
Dave Kreskowiak wrote:
Huh? Wha'dat?
Very cool way to log stuff.[^] Though I only log non-secure info. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
It looks cool, though it appears to be cloud-based logging and aggregation? Damn it! :mad: I can't use it. :mad: Security would throw an epic temper tantrum. It took SIX MONTHS of thrashing those guys to get authorization to have a 3rd-party stand up TWO SERVERS in Azure to be managed by that company and we would install a client app on a dozen machines that connects to them and feeds them data all day for analysis. And that wasn't even HIPPA regulated nor business critical stuff either! They're heads would explode if I showed them this thing.
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave Kreskowiak -
Garth J Lancaster wrote:
I LIVE for that post, Marc
Actually, what's worse is that one of them said the UI (Javascript/HTML hosted in a CefSharp browser client) was ready for QA, so I volunteered to pre-QA the UI before we sent it over the fence to the "real" *cough* *cough* QA people. An hour later, I had 8 pages of bugs. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Oh nice, give the old bastard who has spent years being nitpicked by QA a shot at your first UI :laugh: Don't get me wrong I think QA people are essential but what a bunch of pedantic, anally retentive, irritating, annoying and bloody persistent sods they are.
Never underestimate the power of human stupidity RAH
-
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
The only good case I found for empty try-catch blocks, when your error handling (logging, emailing, whatever it is you do) goes awry :sigh:
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Oh nice, give the old bastard who has spent years being nitpicked by QA a shot at your first UI :laugh: Don't get me wrong I think QA people are essential but what a bunch of pedantic, anally retentive, irritating, annoying and bloody persistent sods they are.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
Oh nice, give the old bastard who has spent years being nitpicked by QA a shot at your first UI
I must admit, I took great sadistic pleasure in the process.
Mycroft Holmes wrote:
but what a bunch of pedantic, anally retentive, irritating, annoying and bloody persistent sods they are.
Yeah, aren't they wonderful? :) Honestly, once I started to learn how to work with QA (part of which was, don't rely on them accurately telling you what they did to break your software), I started enjoying the process, because it did improve the quality of the product, as well as my code and I learned better architecture (ok, fancy word for automatic logging) as well as a result of my QA experiences. The best thing though was when we got to a point of working together, and I could ask them "I found this weird bug in my code and I can't figure out how to reproduce it, could you try?" That was great. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
One petard wedgie, coming up. Welcome to humanity, Marc :-D.
Software Zen:
delete this; -
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Install a mail agent on each server, send all emails to the local agent, and let the local agent send it upstream to the actual relays. Your emails will arrive eventually, even if the whole network is down! You can tune the retry parameters on the local agents to be pretty aggressive on retries.
-
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Marc, In our little system we have email sending configured as a Boolean. Down when we're instantiating the class that sends the email, we look at that. If false, we instantiate an implementation of the class which writes to a local file instead of sending the email. So, we can check content etc in development without the risk of "oops that was a real email address." I wonder if something similar could be wired up for your error condition. Once you're in the catch block, fire off the email send, but pass the magic param which says "write to log/file/send up a flare/whatever."
-
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
At least someone is *trying* to handle/report errors. Better than ignoring them.
-
When your email service, that handles emailing you exceptions, itself throws an exception... Which is then caught by the message processor, that then tries to email you a notification that your application threw an exception... By queuing an exception message... Which gets dequeued on a separate thread... And the whole process repeats itself. :doh: Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
I did something similar. My program connects to a SQL database and when that database connection is broken an exception is thrown and logged to a message processor which also tries to log it to the, wait for it, SQL database. Which then throws the exception again.....
