News for hackers. Stuff that matters.
Re:To code quickly, you must quit coding by thibaut_barrere on Friday November 12, 2010 @10:57AM (#1898028)
Sometimes I download/clone all I need, then go offline. I'm always amazed by how good it feels to go offline!
Re:To code quickly, you must quit coding by portman on Friday November 12, 2010 @01:45PM (#1898666)
I wasn't clear in my original comment: it's not that I require API docs (though they're nice), it's that I require the API itself, usually a REST web service, or in the case of mapping, a bunch of remote resources (images and JavaScript).

When you say you "download/clone", are you talking about just the docs, or do you actually clone the API locally?

For example, create a local, mock Twitter OAuth API so that you can program against the Twitter API without being online.

I'm genuinely curious. I like the idea of going offline, but it seems like it's not worth the effort if you're working on applications that are codependent on network APIs.

Re:To code quickly, you must quit coding by Jasber on Friday November 12, 2010 @04:28PM (#1899348)
I run into this problem and my solution has been to block distracting sites. This gets me 90% of the value of being offline without taking required APIs offline.

I wrote this to help: https://github.com/bradjasper/focus

Re:To code quickly, you must quit coding by thibaut_barrere on Saturday November 13, 2010 @04:00AM (#1900604)
I was talking about the documentation - but for APIs, I create mocks.

For instance my work last week relies on an API that requires a VPN connection AND a windows machine.

I tested and mocked the API on windows, and now work offline, without the VPN nor Windows.