That was my impression too. For someone that smart in a technical field, some things just seemed a little to casual or didn't make much sense. Deleting your bash history because there might be passwords in it? I generally give the benefit of the doubt to the guy in his position--maybe he was in a hurry or got comfortable being one of the chosen few super users--but, you have to think wtf.
At a company like that where IP is highly valuable and you are paid handsomely, you know right off the bat that every character of code you right belongs to the company before even seeing employment and/or confidentiality agreements.
Dating another woman or stuffing a large object in your trunk late at night right after your wife dies, does not look good. You may very well be innocent, but it doesn't look good.
Use the --defaults-extra-file to point to a file containing the password and stop the madness. At least that is what I think should be done if entering the password is inconvenient or not feasible (like in an automated script)
At a company like that where IP is highly valuable and you are paid handsomely, you know right off the bat that every character of code you right belongs to the company before even seeing employment and/or confidentiality agreements.
Dating another woman or stuffing a large object in your trunk late at night right after your wife dies, does not look good. You may very well be innocent, but it doesn't look good.