Network engineers don’t have any free time. Those other 6 claimed it was a network problem and we are having to prove it’s not.
Remember, when in doubt: “It’s a DNS issue”
DNS takes 3 seconds to respond: I still need you to prove it’s a problem with DNS.
Thank god for bcc-tools.
Windows Admin: Its updating
2 hours later: “it’s reinstalling”
3 hours later: Ok look, more updates.
6 hours later: blue screen of death; has to setup windows again
…installs more updates. No postpone.
… and the recursion has begun. #howItIsToBeAWindowsUser
Linux -> it’s installing dependant packages
“It’s compiling” -> Why programmers have wack hobbies.
Windows User: Its loading
Start sim at 8pm (ie, when nobody else is using the shared compute resources) --> jack off for 7 hours while occasionally checking that the sim hasn’t crashed --> check my results when sim finishes at 3am
A hard day’s work in the life of a simulation engineer
sounds like an easy job to me. but i think thats not everything you do all day long.
but ehmm… are you hiring?Yeah… I made the mistake of looking for more work early in that job and got the dead time filled up pretty quickly. I quit that job and I’m a grad student now, but they probably are still hiring. It was an airforce engineering contractor job in Florida, so it’s not very hard but it’s an employees market due to strict degree/nationality hiring requirements and general unpleasantness of living in Florida
My first job in IT required that I run this EDI import process every morning. It was a custom in house solution that extracted the EDI files loaded them in to a SQL database, which then feed them into our ERP system. After my first month I had it totally scripted, but still had to monitor it. So, I would come in, kick off the VBS and read the news, catch up on stuff, and generally have an hour or two to just relax. Then we upgraded to SQL 2008 with brand new hardware and the process only took a couple of minutes. I still miss those mornings.
