under pressure

This month I've been busy working on a new feature for my company's book club websites, most of which are managed by one server. I spent my first few months creating internal tools, scripts, and emails, so I wasn't as familiar with the user-facing codebase as the other web developers. But we needed to mitigate our bus factor, so I decided to bite the bullet. I wanted to better understand how the different pieces of our web stack worked together anyway, and this was a small feature that touches a lot of parts of our web architecture behind the scenes. (I'll write more about the actual code later.)

One of the most important things I realized during this whole ordeal has already been written about:

Nothing gets done when you interrupt an engineer.

We have an open office plan and just moved to a smaller building. The view is nice, but there aren't that many corners where developers can run away and be alone for a while-- places where we can get guaranteed uninterrupted focus time.

I usually like chilling with my coworkers, and a lot of them are naturally social as part of their jobs (marketing, customer service, etc). So I didn't really notice this aspect of our office until this week. Specifically I didn't notice until it was crunch time on Friday afternoon, I was concentrating on debugging a big issue that came up at the last minute, I was interrupted for the fifteenth time about whether we were going to have something ready for release that night, and everything I was trying to keep track of flew out of my head. Again.


My office spirit animal: a bunny falling over at work Me yesterday, my concentration broken again

My project manager is super understanding and tried to run interference for me, but there's only so much you can do on Friday at 5pm when everyone wants to hang out and unwind while you need to get something out the door. (We have a "No Releases on Friday Night" rule, but our other option was releasing on Sunday night and putting out fires during our Halloween festivities the next day-- I put my foot down on that one.)

I managed to debug the issue and do the release eventually... after the office emptied out a little bit.