Working For The Weekend

4 min read

I actually wasn't planning on working at all this weekend. Honest. I was annoyed Friday night because the person taking over for my host for the apartment was making a racket past 2 am when I had planned on going to sleep at a reasonable hour and getting up early to spend all of Saturday cramming on algorithms. Instead I gave up on my plan and ended up getting up at 4 pm. The ironic thing is I just went to a "sleeposium" on Thursday during work to get tips on sleeping better. This was one of the things the guest speaker advised against.

I didn't plan on coming back for the night to make up for all the time I lost. I left around 6:30, thinking I might get food on the way. However, as usual, I ended up just going to the microkitchens for food. It's surprisingly easy not to go hungry given how much food is left over at the end of the week and just by the huge number of microkitchens in the building. I'm particularly fond of the pepper jack cheese sticks, M&M's, and small cans of V8 juice.

After snacking for a bit, I walked to my desk, looking around for a good whiteboard to use to practice whiteboard coding. One was too small, a few others had writing all over them, and the one in my office was just inconveniently placed in the room such that I'd have to lean over desks and drawers to write anything, but that also had important-looking diagrams on it.

I kind of wanted to look at my code from Friday more than study since my tests were failing for bizarre reasons. I managed to get a lot done that day including getting 3 changelists approved and submitted, which is a new record for me, and I even resolved my first assigned bug. Still, I wasn't too happy about leaving with broken code but my manager actually came into my office to tell me I should go home since it was kind of late.

It's bad because GDB doesn't understand Go very well. The error logs were pretty lacking. For a while it was even throwing blank errors so I had a vague idea of where it was failing (no specific line number) but no clue as to why. Cue good old printf debugging from the early days of my CSE courses. 

I actually did manage to figure it out by 5 am and confirmed the majority of my code was working as expected. I kept going and confirmed all but one small piece was working by 8 am.

I decided since I was hitting a spike in productivity to file a bug, solve it, find another issue in code that wasn't mine, fix it, solve another bug assigned to me, and start the review process for the code I finished verifying last night. Eventually I burnt out around 2 pm and took a nap in one of the "bunk beds" on the second floor -- only to get woken up 30 minutes later by 3 girls just wandering around and looking for a place to hang out which for some reason had to be right where I was sleeping-- and this definitely isn't a small building.

Pretty sure I was making something along the

lines of this expression after getting woken up

It's good I got a ton done but now I'm a little worried I won't have as much to do this week other than -- shudder -- study. I don't want to study because then I'll get stressed out when I realize how unprepared I am to do REAL interviews in 4 weeks but if I don't study then I'm basically throwing my golden opportunity out the window. Meanwhile I'm also supposed to be scheduling mock interviews and obviously the real ones soon...

Previous Post Next Post