Listened to this on Friday. Thank you for reinforcing what I have been saying for about a year now around my company.

People in production brings in equipment that requires network connection and ports open to a cloud server, but does not inform us of these needs until after the equipment has been installed and wonders why its not working.

"Well no wonder why it is not working. We have to run a network connection into a production environment, give your equipment (that I just met, potential security issue) an IP address, and open ports to a cloud system that I have no idea about and no control over. All because you did not value IT enough to include us in the decision making processes to figure out if it would be compatible with our environment."

@guyinpv said in Was It the Last IT Guys Fault:

@Carnival-Boy said in Was It the Last IT Guys Fault:

Probably the main thing that puts me off moving jobs is that it means moving in to someone else's shit, which you then have to spend months, or even years, sorting out.

This is actually my favorite part.

If the new boss is open to upgrades and fixing everything up and implementing better documentation and records and stuff, it can be a lot of fun "restoring" the old thing, or "modernizing".

To me it has the same appeal as restoring a car or a run down house project or something. There is some enjoyment in tinkering everything back to life and putting on a fresh coat of paint and blowing out the dust. Plus there is just a lot of work to do, versus when everything is smooth and automated and you find yourself getting bored.

I agree, the "fixing it" is one of the best parts.