E
@joe.edwards said:A former colleague of mine once requested adamantly that if he accidentally passed null to one of my functions, it needed to log where the null came from. I had difficulty explaining that my function would have no idea where the null came from, as it was the only parameter passed into it. After some back-and-forth, I ended up grabbing a stack trace if debug symbols were enabled, and logging the frame above it. That attitude betrays a severe lack of understanding computer programming! Though it does remind me of a colleague of mine who literally came up on punch cards since PCs didn't exist when he got his degree, to do his assignments he literally had to mail decks of punch cards and wait days for the output to be mailed back, (actually it was a wonder that he was still working at all.) This "programmer" had the strange idea that testing was a task resembling janitorial duties, and was unfit for real programmers, and should be handled by interns and the newbies. Never-mind that we didn't actually have a QA department to trow code over the wall to, and only one support tech who was represented to clients as a team of 10.