> I find coding offline more constructive - my most productive coding sessions are on the train. Getting to focus on what I'm trying to achieve without getting

> I find coding offline more constructive - my most productive coding sessions are on the train. Getting to focus on what I'm trying to achieve without getting distracted is important and useful. I do this as well. Airplanes and underground trains are some of my favourite places to program. > But debugging is impossible without the internet, I find. Working out what an error means from just the error description and the source code of the library is bloody difficult. I find most bugs by reading the code. The error doesn't mean anything. You have decided that the computer did something unexpected. Rather than assume the computer is wrong, you need to assume that it is correct, and that some part of your assumptions were wrong. A friend of mine was trying to hash some content, but every file it hashed was `da39a3ee5e6b4b0d3255bfef95601890afd80709` so he tried all sorts of stuff. If you know what the SHA-1 of an empty string is, then you're like google, but if you just read the code, you'd see a `||` instead of an `&&` that meant that the `read_file()` never occurred.