3 ms·
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 di
by marcus_holmes 10y ago
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.
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. Googling the error message gets better results immediately. A friend and I were talking about this, that maybe we should just use UUID's for error messages and write the error description in Stack Overflow, since that's where they'll end up anyway.
- technomancy 10y agoI think the difficulty of debugging just depends on the problem. If your problem is largely composing third-party libraries and services, then yes, it's extremely difficult to do when disconnected. But in my experience if it's mostly code you control, and you're iterating on the design and flow of the execution, then being online is mostly just a distraction.
- marcus_holmes 10y agoyeah mostly it's plumbing these days. I can debug my own code OK, but debugging a weird library call is hard without the tubes.
- cbhl 10y agoPlease consider a "horse battery correct staple" style error message, because sometimes one (say, a TA, or a friend helping a friend with a CS assignment) will receive that error message in a JPEG taken with a cell phone camera.
- marcus_holmes 10y agohaha, yes, a use case we hadn't considered. this is probably why no-one's done this, and in fact most error messages are "horse battery correct staple" style messages :)
- geocar 10y ago> 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.
- iamflimflam1 10y ago1.That can’t happen. 2.That doesn’t happen on my machine. 3.That shouldn’t happen. 4.Why does that happen? 5.Oh, I see. 6.How did that ever work?
- cmplxconjugate 10y agoThat's always the tough one: "How did this even work in the first place...."