Notice: Trying to get property of non-object in /var/www/sett/includes/renderpost.php on line 51
The Silver Lining in Taking Breaks from Work - Tynan
hide

Read Next

The Point of No Return is a Good Place to Be

I now know better than to estimate the time moped projects will take. A quick half hour job turns into a frustrating afternoon after just one or two minor speedbumps. And that's what happened today.

One of my tires went flat last week, but instead of just replacing the tube, I ended up buying new wheels, tubes, and tires, because my old ones had spoked rims that weren't quite as straight as they once were, and didn't quite have as many spokes as they once had.

To ease into the work, I decided to do the front wheel first. Taking off the back wheel requires removing the belt, chain, brake cable, and then you have to take the transmission out of the hub. The front wheel should only require removing the brake cable.

The Push

On Made of Metaphors

My job at Bungie these days is about one core piece of technology we use to make our games. It's a system that all the artists, designers and sound designers use to get their work into the game. So, like any technology job where you're building a product other people use, there are two kinds of work: the work of building the technology and the work of supporting the people using it.

Things have been busy enough lately that I was trying to focus just on the coding and not do much support work. It wasn't really working out. All around me the artists, designers, and sound designers were struggling with issues while I was trying just to plow ahead on the coding work we need to get done. When the support work boiled over and I had to stop and attend to it, it took a ton of time and effort. Because I'd been burying my head in the sand trying to get code written, I didn't have any context for what was happening with the users. If I had to help someone, first it took me a good half-hour of asking random people questions just to have enough context to even understand what the problem was and what needed to happen.

I couldn't ignore the support work, though. Eventually I had to turn my attention towards it, and so I did, one week, and it consumed basically my entire week. I got just about nothing else done. It was frustrating seeing the coding work pile up, so my response was to keep trying to minimize my involvement in the support work. I'd do as little as I could get away with, try to hand off problems to someone else. Bu it didn't seem to actually help. It still took a ton of time just to figure out enough about a problem to know how to hand it off to someone else, and if anything that ramp-up time was getting longer.

* * *If you've ever watched the Tour de France, or the road biking events in the Olympics, or ever seen any group of people riding road bikes together, you've probably noticed they tend to cluster together in a compact formation. They're not just riding close together because they like the company (and the increased risk of crashes and injuries.) No, they're riding close together because of drafting.

Rendering New Theme...