In college, I misspent a few summers working as a Desktop Support grunt. I've always been hesitant to leverage this experience in my professional life—one, tech has changed a lot in 20 years; two, I don't want to be that developer, stepping out of his lane with flimsy-ass qualifications and the confidence of a Mediocre White Man™.
But for the second time this summer, I've managed to help resolve a security software issue with a basic problem outline and spot support in case comments from the IT team. Avoiding the need to remote-in (or even live chat!) has saved hours on both ends of the collaboration, and I think fostered trust and cross-departmental communication.
It's a good reminder for me not to hold back on bringing my full range of skills to bear at my Day Job—even when note specifically called for—as well as a nice moment to be grateful to work at a solutions-oriented company where open communication and low egos are the norm.
But for the second time this summer, I've managed to help resolve a security software issue with a basic problem outline and spot support in case comments from the IT team. Avoiding the need to remote-in (or even live chat!) has saved hours on both ends of the collaboration, and I think fostered trust and cross-departmental communication.
It's a good reminder for me not to hold back on bringing my full range of skills to bear at my Day Job—even when note specifically called for—as well as a nice moment to be grateful to work at a solutions-oriented company where open communication and low egos are the norm.