My time spent developing my passion project hasn’t been continuous since the time I first started working on it. The first iteration lasted about a month and was a mad rush to cobble something together to mark the momentous “milestone” of 100 blog posts. I then spent the next couple months experimenting with Silverlight managing to replicate and extend the base feature set out to a point where I felt I was making progress. I then went on a 6 week hiatus from developing Geon to work on The Plan which, whilst making me a decent sized profit, never turned out to be the ticket to freedom I had hoped it would be. After taking a month off after that and coming back to look at Geon I couldn’t help but think that I was going about things in all the wrong ways, and came up with a completely new design.
This, I’ve found, is a common trend for me. Unless I continually work on a project I’ll always end up questioning the idea until I end up wondering what the point of doing it in the first place was. Initially this was quite good as whilst the first few iterations of Geon showed solid progress they were in all honesty horrid applications. However it was devastating for overall progress as the paradigm shifts I underwent during these times of developmental absence meant that the new vision was wholly incompatible with the old and I could see no way other than starting anew to get them back in line again. This is why the first2 iterations didn’t have any form of user logins and the third was such a horrible process that I don’t blame anyone for signing up for it.
I had thought that short breaks were immune to this idea as I had often taken a weekend or two off when a family event called or I was starting to feel burned out. However I hadn’t had the chance to do much work on Lobaco over the past 2 weeks thanks to me being otherwise occupied and those little tendrils of other worldly perspective started to creep in. Maybe it was the booze fueled weekend where I had a list of 5 other potentially marketable ideas or maybe it was just me pining for another break but suddenly I felt like there was so many other things I should be doing than pursuing my almost 2 year old idea. I let myself think that I could take part of the weekend off to work on one of those ideas but for some reason I just kept working on Lobaco.
I’m not sure if it was my persistence or hitting the submit on my application to Y-Combinator that did it but instead of pursuing those ideas that had tempted me all week long I just fired up Xcode and started plugging away. Whilst not my most productive weekend ever I did manage to tick off 2 more features for the iPhone client, leaving about 3 to go before my deadline of the end of March. I think the combination of a solid code base (that has all those rudimentary things done so I don’t have to spend time researching them) and almost half a year of iOS development under my belt is enough to keep the momentum going, making sure I don’t give up on this version until it reaches 1.0.
I used to think that time away from coding was just as valuable as time spent in code but that doesn’t seem to be holding as true as it used to be. Sure my first breaks led to radical changes in my vision for the end product (and is responsible for the Lobaco that exists today) but once you hit that sweet spot time away can be quite destructive, especially if you’re as prone as I am to distraction by new ideas. Thankfully the last 6 months of momentum aren’t lost on me and 2 weeks away wasn’t enough to distract me from my end goal. It would have been to easy to start procrastinating again without realizing it.
I woke up this morning to a beautiful day. The sun lit up my house with a nice warm glow and I felt rested as I jumped out of bed. Casting a cursory glance to my clock showed that I had overslept by an hour, and this beautiful day was actually just the sun doing it’s usual thing, and I was late for work. This in itself isn’t a bad thing, I can make up the time whenever I want. However the drive to work at this time was a lot more congested then what I’m used to, with what is usually a 15 minute trip turning into over half an hour.
Casting my mind back a few months I remembered someone speaking to me about their working from home arrangements and how well it was working out for them. The idea struck me whilst I was stuck behind several other people caught up in the rat race: If a majority of people worked from home instead of a central workplace wouldn’t there be countless more benefits apart from the convenience of not having to go to work in the mornings? I know I’m not the first to think of this idea but it’s something that I felt could definitely have an impact after experiencing the horror of rush hour again after years of missing it.
The first benefit I can think of is happier employees. You’d be able to set up your own workspace as you saw fit and no one would complain if you showed up to work in your pajamas (as long as the webcam is from shoulders up, of course!). We all work better when we feel happy and the numbers show that about two thirds of telecommuting employees increase their productivity. I think this comes down to freeing people from the need to “look busy” whilst their at work and allows them to focus on actually completing tasks rather than fighting the fires that crop up at the office. I know my fiancée said she got a lot more work done in 4 hours at home then she did at the workplace, and she could take a break to watch TV on the couch; something she just couldn’t do at work.
There are also numerous cost savings for the organisation as well. Requiring less on-site infrastructure means that companies can save on things like air conditioning, facilities management, computing equipment and so on. Most telecommuting employees will use laptops which make a cheap desktop when combined with a docking station. For those that use their own computers the benefits are the same, since the company would only have to provide on-site resources if required. Companies that have implemented schemes such as this have already seen massive savings and it’s no surprise that they’re the ones still alive during these hard economic times.
One of the more obscure (and unfortunately intangible for the company until carbon trading is implemented) benefits of having a majority of employees working from home is the reduction in green house gas emissions. Whilst I don’t have any hard numbers on what the impact would be I can tell you this: In an internal combustion engine the most inefficient time for the engine to run is at idle, and this is how companies like Honda increased mileage considerably with their technologies like i-VTEC. Traffic jams cause cars to stay at idle for extended periods of time and the constant acceleration/deceleration only serves to cause excessive wear on all engine components. Spending less time in these inefficient cycles would see a reduction in green house emissions, something I’m sure everyone can appreciate.
This is not to say that it’s all roses when it comes to telecommuting, there are definitely many challenges that employees and employers must overcome before they can see the benefits. One of the biggest hurdles I see for employers is the transition from a “on the clock” model of performance to a metric based one. Employers often have a hard time figuring out how to objectively judge how their employees perform and the introduction of telecommuting forces their hand on this issue. There’s also that issue of face time with your employees and many companies put a lot of value on this. I’ve found that this is usually just because “that’s the way it’s always been done” and once they’ve done the analysis their view of telecommuting shifts very rapidly, and benefits the other non-telecommuting employees as well.
If you’re considering asking for a working from home arrangement I’d recommend this resource guide from CIO.com. There’s a lot of good information there on the pros and cons of implementing such an arrangement and it’s also aimed at the managerial level so you won’t have to rewrite it for your boss 🙂
Now to make up that hour of work I missed….