• MelonYellow
    link
    fedilink
    English
    arrow-up
    13
    ·
    5 months ago

    Sometimes I get called out for pacing around when it’s like no! I’m actually doing stuff… except I’m being forgetful and inefficient so I keep having to backtrack >_<

    • I was hired at a small company a number of years ago. Contract-to-hire. One of those “we want to see you prove yourself before we actually hire you” deals. My role was to take over all of technical operations (cloud architecture, sysadmin, desktop support, the whole deal), so that the CTO didn’t have to do it all himself.

      One time - about a week in - I spent the entire day playing with kinetic sand in the main lobby (which was in full view of every developer and the CTO). Mostly, I was building little bricks (something like 0.5x1x2cm), and stacking them in a 2 sided 90 degree wall.

      When asked what I was doing by several people throughout the day, I said “I’m rebuilding your network”. I’m certain I looked like a crazy person. Honestly, it’s not a totally invalid assessment in general, even now.

      What I was actually doing was planning out the subnets, ACLs, and general routing for a series of servers (web front-ends, api servers, DB servers, etc), and weighing the pros and cons of AWS LBs vs HAProxy for various applications.

      Over the next few days, I built out the new network and started migrating legacy servers into it. I demo’d the process and accompanied documentation (which I mostly kept in case I had to build another network, or rebuild this one after some catastrophic total loss), and they seemed impressed.

      My 3 month contract was converted to direct-hire within 3 weeks, after a number of other enhancements (like centralized ssh auth via OpenLDAP - rather than everyone sharing the same default user RSA key - and total systems monitoring via Nagios). Each one came with about a day’s worth of playing with some fidget or fixing some non-technical thing (like hanging a bunch of framed items in the lobby, which they’d been meaning to do, but wasn’t a high priority, especially for the technical staff).

      They’d have had all the reason in the world to assume the new guy was full of shit and was about to wash out, but after that they assumed that when I looked like I was majorly slacking off (usually well away from my desk, tinkering with something mindless) that I was about to build some new thing into the network, or up-end a process, or some other crazy (but ultimately useful) thing.

      They definitely didn’t mind when I would pace and talk to myself like a nut-bar (which I did/do frequently).