hide

Read Next

What I Learned From Two Frustrating Days of Not Working

For two days, I didn't do any programming for SETT. The morning of the first day I was busy with other high priority stuff. I finished that up, ate lunch, and decided to work on SETT. But then... I didn't. I answered emails, played my violin, researched some stuff, and bought some plane tickets. I wasn't unproductive, but I was not working on my top priority, and I knew it.

That whole day I was tired, so I went to sleep early and woke up fresh the next day, ready for a full day of programming to make up for my prior shortfall. But again, I didn't program a line of code. I didn't even open up my code editor.

The next day I woke up mildly panicked. Two days of lost productivity is a bad thing, but worse was that was that I felt as though I lost my edge. Part of me wanted to work, but another part of me was avoiding it at all costs. It felt as though all this discipline I'd been building for the past couple years was crumbling to nothing. How disciplined could I be if I was unable to spur myself to action for two whole days?

Okay, let's diagnose this, I thought. I opened up a text editor and asked myself what my problem was. Why wasn't I working?

The 120-Hour Workweek - Epic Coding Time-Lapse

On nickwinter.net

Last week I set out to see how many hours of programming work I could do in one week on CodeCombat, our multiplayer programming game for learning how to code. I clocked in at 120.75 hours. Here's the epic time-lapse video I generated from Telepath (watch in 1440p if you can):

So what did I learn from this experiment?

Adjustable height desks are amazing.

I bought one from Ergo Depot a few days before. I must have switched between sitting and standing fifty times last week. I would never have survived otherwise.

Rendering New Theme...