3 min read
Today I made more progress on coding and bike riding. I've been in the testing phase for 2 entire days now and all the tests are passing but I'm still skeptical that they're testing the right things. It's difficult to test whether a program meant to modify jobs on a distributed system works without jobs and without a distributed system for testing.
Seeing as I couldn't make much more progress without checking in with my manager and asking questions regarding the tests and he was in a long meeting, I took a break to practice riding the GBikes. It was actually raining when I practiced, which is surprising since it rarely ever rains in California. It was more like the annoying kind of rain where it can't decide if it wants to actually rain or not. That didn't stop me from wanting to practice.
I found a bike and got going after not too much difficulty and decided to do a loop around one of the LinkedIn buildings (their headquarters is actually right on our campus). I think I must have almost met my goal of riding without stopping for 5 minutes. I was able to ride over speed bumps and around corners but I had to stop for approaching cars. I must have looked like a drunk person trying to ride a bike but I'm slowly starting to care less.
I was even able to do a U-turn a couple times but it's like the bike still has a mind of its own. Fortunately I haven't gotten hurt (yet) and I was even able to ride in the bike lane halfway to Charlie's which is about a mile away from the building I'm in. Although it's frowned upon I think, it made more sense for me to ride on the sidewalk and not get hit by a car so I did that the second half of the way there and all the way back. I can just barely ride in a straight line so I'm a hazard on the road. Here are videos proving I actually kind of know how to ride a bike. These are the ones from yesterday so I'm still pretty wobbly.
Riding around the cul-de-sac. That building in the first picture is where I work
As for tomorrow, I get to find out if my very first CL gets considered for review by another team. I'm hoping all goes well but I'm doubtful seeing as it's not a critical chunk of code and a large chunk to review at that.