This article resonates with me on so many levels. When I started working on Semantics3 early this year, I spent many a day frustrated that I was barely achievin

This article resonates with me on so many levels. When I started working on Semantics3 early this year, I spent many a day frustrated that I was barely achieving 50% of the productivity that I was capable of and I felt quite miserable about it. Here are a few things I did to get things back on track: 1) Moved Closer to Work: Daily long journeys are massive downers. When I awake in the morning, I often feel the urge to hit my laptop right away and channel all the early morning enthusiasm towards work. College years were ideal on this front because there was never anywhere to be (I wasn't too inclined towards attending classes ;)). Anyway, now, I live 20 mins away from work. 2) Stopped Listening to Music (especially during the few hours after I awake): I'm a music buff and perennially have music in my ears. But I find that music often blocks useful thoughts; letting the mind wander leads me down interesting channels, be it more ideas for my startup or even bugs in my code that I discover by merely thinking about the previous day's work (Rob Pike's "Best Programming Advice" comes to mind). Few things are more satisfying than stumbling on these nuggets! These days, I restrict music to certain times of day, such as my ride home or during certain phases during the work day. 3) Found Time at Work Alone: I like getting to work a couple of hours before everyone else, before any distractions kick in. For some of you, staying at work an hour after everyone leaves, lunchtime, or even spending an hour at home to finish things up might do the trick. Those power-charged hours make me feel like I've given that extra bit to my day. On a related note, check out PGs "Maker's Schedule, Manager's Schedule" (www.paulgraham.com/makersschedule.html)