How to be in IT
retained text
I had a guy today complain that something wasn't working in his email client. Normally, I don't bother troubleshooting these things and have someone else handle them. But I figured, whatever, I've got the guy on the phone, so let's take a look. We spent about 10 minutes going through different things to figure it out. The whole time, I'm just saying, "Click this" or "Try that." Finally, after we got it fixed, his tone changed, and he said, "I feel like you didn't really know how to fix it, and we just randomly stumbled through things until it eventually worked." My response: "That's IT. You need to be willing to try to break things, and eventually, you'll figure out how to fix them." While, in reality, there are experiences where we know exactly what to do, and others where we're making a more educated guess. Looking back, I think some of the biggest things I've fixed or learned came at the expense of potentially breaking a whole lot more. So, is the only difference between an IT person and, say, an accountant, that we're willing to gamble and press that button that could blow up the entire network?
document fetched 2026-11-12 00:39 · canonical https://reddit.com/r/sysadmin/comments/1xt4cqp/how_to_be_in_it