<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>This is the offical blog for DesksNear.Me — helping freelancers escape the home office, one day at a time. Book desks at local coworking offices for any workday of the week.</description><title>DesksNear.Me Blog</title><generator>Tumblr (3.0; @desksnearme)</generator><link>http://blog.desksnear.me/</link><item><title>Well, we were #1 - for a few hours at least.</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_laqvjz3rqe1qeqkwwo1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;strong&gt;Well, we were #1 - &lt;/strong&gt;for a few hours at least.&lt;/p&gt;</description><link>http://blog.desksnear.me/post/1380790821</link><guid>http://blog.desksnear.me/post/1380790821</guid><pubDate>Sat, 23 Oct 2010 09:16:47 -0400</pubDate></item><item><title>RailsRumble Retrospective</title><description>&lt;p&gt;&lt;a href="http://desksnear.me"&gt;DesksNear.Me&lt;/a&gt; was dreamed up in a second by me, refined by Keith Pitt, Warren Seen, Alex Eckerman, and myself over 4 weeks, and then built and delivered in less than 48 hours by all of us during the RailsRumble competition.&lt;/p&gt;
&lt;p&gt;I wanted to briefly go over a few of the things that were good and bad about our adventure thus far.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What went right:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Having a fantastic team is key&lt;/strong&gt;. I was fortunate to work with some very dedicated, talented, and passionate people.&lt;/li&gt;
&lt;li&gt;&lt;span&gt;We&lt;strong&gt; got a reasonable amount of sleep&lt;/strong&gt;. I did RailsRumble in 2008 and stayed awake for 57 hours straight. More time to code does not mean you get more code done. After about 18 hours of coding straight, you stop thinking clearly, make mistakes, and ultimately freeze up. Our project deserved more than this, so we got our sleep and focussed in our respective days.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;For the periods where our differing timezones allowed, &lt;strong&gt;we kept a 4-way Skype chat open the entire time&lt;/strong&gt;. This kept us efficient and focussed because we could hear each other working, didn&amp;#8217;t get bored/distracted/lonely, and if we got stuck, help was only a question away.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;We worked in &lt;strong&gt;two 24-hours iterations&lt;/strong&gt; and aimed for (and almost achieved) our minimum viable product in the first iteration.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;We &lt;strong&gt;fleshed out our backlog&lt;/strong&gt; and planned our weekend strategically.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;The &lt;strong&gt;first thing we did was deploy&lt;/strong&gt; and we deployed very regularly so we wouldn&amp;#8217;t be scrambling at the end.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;We &lt;strong&gt;covered all functionality in integration tests&lt;/strong&gt;. We&amp;#8217;ve had no recorded 500s and less than 1% of requests are 404s.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;We&lt;strong&gt; set up a CI server&lt;/strong&gt; (in that same 48-hour period) so we could move agilely and have shared knowledge and responsibility for keeping our test suite thorough and green.&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;What went wrong:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;We &lt;strong&gt;did not anticipate how quickly we would get attention&lt;/strong&gt;. Because of this, our naïve implementation of our geocoding (all done server side) hit the Google Maps API limit in about two hours. We provisioned a new IP, and hit the limit again an hour later. Fortunately, &lt;a href="http://twitter.com/#!/thormitchell"&gt;@ThorMitchell&lt;/a&gt; got in contact with us and white-listed our IPs. A big thanks to the Google Team for helping us out here.&lt;/li&gt;
&lt;li&gt;We &lt;strong&gt;had to rewrite our search functionality three times&lt;/strong&gt; because our assumptions about how intuitive the search would be were wrong. Luckily, thanks to our CI server and quick thinking, this didn&amp;#8217;t waste more than a few hours.&lt;/li&gt;
&lt;li&gt;We &lt;strong&gt;lost about 12 hours across the entire team trying to test OAuth logins&lt;/strong&gt;. We ended up switching plugins and reworking our test suite too many times than we can count and I think this really hurt us. We didn&amp;#8217;t get to about 3-4 features we were hoping to get into our final product. In the end, I&amp;#8217;m glad we persevered, after seeing how many final RailsRumble entries simply 500ed when I tried to log in to them.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;What went REALLY right:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a href="http://twitter.com/#!/collis"&gt;@collis&lt;/a&gt; from &lt;a href="http://envato.com"&gt;Envato&lt;/a&gt; got wind of our application in the first hours of it&amp;#8217;s life and tweeted it. We are pretty sure this is the catalyst for a whole series of successes, ultimately leading to (in these first 4 days) 11,981 visits, 41,309 page views, a HackerNews front page article, 354 users, 119&amp;#160;&lt;strong&gt;real&lt;/strong&gt; self-listed workplaces, and 63 real bookings. We are incredibly excited with these results. We&amp;#8217;ve received consistently positive feedback and several reports of freelancers who made bookings this week turning up at locations such as &lt;a href="http://thefrontiergroup.com.au/"&gt;The Frontier Group&lt;/a&gt; in Perth and &lt;a href="http://engineyard.com"&gt;EngineYard&lt;/a&gt; in San Francisco.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://twitter.com/#!/thormitchell"&gt;@ThorMitchell&lt;/a&gt; tweeting to me and coming to our rescue about 5 minutes before we were going to pull out of the competition in order to fix our geocoding issues. I&amp;#8217;m not kidding, we were on the phone to one of the competition organisers as it happened.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;I&amp;#8217;ve gone on long enough now. Thank you all so much for helping us come this far, and please continue to do so. I think with your help we can reach the critical mass needed to make this site a thriving, self-sustaining, and wonderfully useful community of coworkers!&lt;/p&gt;</description><link>http://blog.desksnear.me/post/1371325896</link><guid>http://blog.desksnear.me/post/1371325896</guid><pubDate>Fri, 22 Oct 2010 00:45:00 -0400</pubDate></item><item><title>Desks Near Me</title><description>&lt;p&gt;DesksNear.Me is a fantastic way for nomadic freelancers, roaming contractors, or other coworkers to find a place in which they can be productive.&lt;/p&gt;
&lt;p&gt;There are plenty of companies out there which are happy to lend out a spare desk or two to people and even more companies whose entire business model is based around providing these work places. &lt;/p&gt;
&lt;p&gt;Most of &lt;strong&gt;the developers of DesksNear.Me are freelancers&lt;/strong&gt; themselves, so we&amp;#8217;ve been in the position of trying to find somewhere to work besides our home office. So, we love those companies who try to help out. Unfortunately, there hasn&amp;#8217;t been an obvious way to &lt;strong&gt;connect these businesses with their target audiences&lt;/strong&gt; (us!) until now.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;We think we can change that&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;We&amp;#8217;ve been live for only 24 hours, but if you look at the &lt;a href="http://search.twitter.com/search?q=desksnearme+OR+desksnear.me"&gt;20+ pages of twitter responses&lt;/a&gt;, the HackerNews &lt;a href="http://news.ycombinator.com/item?id=1801892"&gt;article&lt;/a&gt; that was &lt;a href="http://twitpic.com/2ym6hp"&gt;#3 on the homepage&lt;/a&gt; within a few hours of being live, and our &lt;a href="https://docs.google.com/fileview?id=0B-93TjyDyC_bZmNmZTNkZGUtMzRkMS00YTc2LWFlODUtZDM1Y2M1OGYwMGI5&amp;amp;hl=en&amp;amp;authkey=CP263Z4N"&gt;google analytics stats&lt;/a&gt; for the first day, it seems &lt;strong&gt;others think so too&lt;/strong&gt;. In fact, we&amp;#8217;ve only been able to find one negative thing about our app, and it was about the HTML source!&lt;/p&gt;
&lt;p&gt;We spent a few weeks planning out how our application would work and had about 200 things on our list. We choose a handful of things to start with, and I think we&amp;#8217;ve done them well. We&amp;#8217;ll have a lot more refinements and features coming in future versions (after the RailsRumble competition closes), including iCal integration, variable desk numbers, official support for paid co-working places (more below), and better workplace management.&lt;/p&gt;
&lt;p&gt;On DesksNear.Me, it is &lt;strong&gt;entirely free to list a free workplace&lt;/strong&gt;, ideal for companies who are helping the freelancing community with a few spare desks and monitors.&lt;/p&gt;
&lt;p&gt;Currently, it is also free to list paid co-working spaces and other similar workplaces that charge for drop-in desks. We think we have a fantastic idea and application and we want to make sure it stays around. As such, we have a few ideas to solve this and one of them is to &lt;strong&gt;charge a reasonable listing fee or percentage of booked desks&lt;/strong&gt; for businesses that use DesksNear.Me to help keep their own business alive. We have a few features and ideas up our sleeves to make it worthwhile for these businesses to pay for their listings, too.&lt;/p&gt;
&lt;p&gt;We don&amp;#8217;t have numbers yet, but any paid co-working spot which was added during the RailsRumble competition will have a discount on any charges we bring in. You helped us gain the attention we think we deserve, and as such we want to look after you.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;br/&gt;Bodaniel Jeanes &lt;/p&gt;</description><link>http://blog.desksnear.me/post/1345942557</link><guid>http://blog.desksnear.me/post/1345942557</guid><pubDate>Mon, 18 Oct 2010 16:46:38 -0400</pubDate></item></channel></rss>

