Apologies in advance for the rant but I'm fed up with developers who go to great lengths to re-invent the wheel simply because they don't know how to do something the proper way. They then leave and you pick up the mess.
I'm looking at SSIS packages with a great raft of elaborate error handling using JSON and new database tables, written because someone believed and actually told me that they didn't use sysssislog because you can't write to it yourself from a script or elsewhere in a package. I did say "Rubbish" at the time but as the newbie listening to a handover, I couldn't elaborate.
It results in one package for each dataflow and then a controlling package run by a SQL Agent job whereas the whole lot could be one package with half a dozen dataflows. The overheads are awful.
And this was supposed to be a hot shot developer who could do all the API call stuff in SSIS to get data! Yes and obfuscate it with so much bloat that it's a struggle to follow it.
So my interview question of the day would be - "tell me about logging in SSIS" or "how do you write to the log table in SSIS?"
And if they don't mention using the log procedure from a script (me.log(...) or dts.log(...)) they don't get through!
Thanks for being a place to let off steam!