4 ms·
I have become the resident "hardware guy" in roughly this fashion. When I got the job, my only computer hardware experience was building my own janky PC and hav
by mkaic 4y ago
I have become the resident "hardware guy" in roughly this fashion. When I got the job, my only computer hardware experience was building my own janky PC and having watched 100s of hours of Linus Tech Tips, but when my boss suggested I build a 10,000 dollar workstation for use in our lab, I said yes because it sounded exciting. Fast forward 8 months to the present day and I've been managing CUDA versions on GPUs across workstations, installing and troubleshooting hard drives, moving servers between different locations, and other odd jobs related to our on-premise compute. It doesn't make up a huge part of my day-to-day work, but it's also funny looking back at how I somehow became the "hardware guy" when one my coworkers has background in mechatronics! (this is not a complaint, btw, I quite like being in charge of expensive PC components)
- didgetmaster 4y agoIt is not always bad to become the 'resident expert' on some technology that was not part of your original job description. Sometimes it can help you expand your horizons in something that is really interesting to you. Sometimes it can be great for job security when you are the only one who truly understands some critical piece of the infrastructure. But for every one of those tasks, there are probably two where you can get roped into maintaining some legacy system that is nothing but pain.