News for hackers. Stuff that matters.
Re:To code quickly, you must quit coding by portman on Friday November 12, 2010 @10:51AM (#1898005)
What kind of work do you do that allows you to code without an Internet connection?

These days, I can't go more than 10 lines of code without having to call some API* that requires me to be online.

* Examples from just yesterday: Amazon, Twitter, Facebook, PayPal, GData Contacts, GData Maps, Bing Maps, YouTube.

Re:To code quickly, you must quit coding by zokier on Friday November 12, 2010 @02:04PM (#1898739)
1. Download docs.

2. Code for a day offline with the docs.

3. Test your code (online).

4. Submit a ton of bug reports for the docs.

5. Yay, improved documentation!

Re:To code quickly, you must quit coding by cma on Friday November 12, 2010 @08:51PM (#1899980)
6. Don't receive any monetary compensation for this.

7. Get outstripped by competitors.

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.

Re:To code quickly, you must quit coding by bad_user on Friday November 12, 2010 @11:46AM (#1898217)
I noticed that whenever I have documentation at the reach of my fingertips (Intellisense, awesome API docs), I'm not going through the effort of really reading the documentation and many times I start cargo-culting.

For instance ... if you need to read the Amazon AWS's docs, maybe you're better off searching for and using something like Boto. If the Boto API is too complex to memorize, maybe you're better off constructing a Facade around it that you can remember without going for the documentation every time you want to open an S3 bucket.

Just saying ... lack of easily accessible documentation leads people to do strange things :-)

Re:To code quickly, you must quit coding by jfarmer on Friday November 12, 2010 @12:34PM (#1898397)
He's saying he actually needs to make the API calls, not that he needs to look up the API docs.

If you're building a Facebook app, for example, you need to have Facebook available at all times or it just won't work.

Re:To code quickly, you must quit coding by omouse on Friday November 12, 2010 @11:39AM (#1898192)
Download the documentation using `wget`.
Re:To code quickly, you must quit coding by modoc on Friday November 12, 2010 @12:16PM (#1898336)
He's not talking about documentation. He's talking about making API calls to online services. To test that sort of stuff, you have to be online, and generally you want to test that stuff pretty often as you're building things.

I just did a PayPal API, and the docs were pretty bad/inaccurate, so we had to make frequent test calls to see what the real world behavior actually was.

Re:To code quickly, you must quit coding by portman on Friday November 12, 2010 @01:53PM (#1898691)
RE: PayPal.

It gets worse. There are several situations where the docs say one thing, the sandbox behaves a different way, and the live API behaves in a third, different way. It's a mess.

Re:To code quickly, you must quit coding by jgh- on Friday November 12, 2010 @01:26PM (#1898582)
Surprisingly, there are still applications being written which do not require an internet connection at all times.