Ask HN: Programming on Plane Trips
15 comments
as a 2m / 6'5" person... you are so lucky
I wish I could zip through a set of programming koans on a flight like https://github.com/cdarwin/go-koans without elbowing my seat neighbors to a pulp
if I could even get the table tray down. more often than not i eat with the food on my knees :(
I wish I could zip through a set of programming koans on a flight like https://github.com/cdarwin/go-koans without elbowing my seat neighbors to a pulp
if I could even get the table tray down. more often than not i eat with the food on my knees :(
Try just writing the code without looking up the real API. If you actually see that the official API is worse than what you have imagined, maybe it's better to write a wrapper than ruining your beautiful code.
Similar to Test driven development you can call it beautiful code driven development (DHH wrote rails in a similar fashion).
Similar to Test driven development you can call it beautiful code driven development (DHH wrote rails in a similar fashion).
Why do they require the internet? Can you not run or mock your required services locally?
One of them is still in its infant stages (so requires lots of Googling and package downloads, etc), and the other is a Chrome extension for a specific website.
Could probably try doing the first one without internet and seeing how it goes.
Could probably try doing the first one without internet and seeing how it goes.
Hard to say without details about the chrome extension, but sometimes I write user scripts or scrapers for specific websites, and I often work with a saved copy of a relevant page.
Save some Project Euler problems? https://projecteuler.net/
As a side note, if you're looking to be able to access offline documentation for the entire tech stack for any projects (primary or otherwise) I highly recommend https://kapeli.com/dash (or https://zealdocs.org/ for other platforms).
I also find that when working on a laptop with limited arm mobility and screen size, it's tremendously useful to be able to switch between IDE, documentation, and browser (for localhost review) with a single keystroke. On macOS I use a combination of Karabiner Elements and BetterTouchTools to bind my caps lock key to hide or show my IDE, and other apps to command-caps-lock etc.; having an instant, tactile hardware switch between IDE and non-IDE is almost as good as having double the monitor space!
I also find that when working on a laptop with limited arm mobility and screen size, it's tremendously useful to be able to switch between IDE, documentation, and browser (for localhost review) with a single keystroke. On macOS I use a combination of Karabiner Elements and BetterTouchTools to bind my caps lock key to hide or show my IDE, and other apps to command-caps-lock etc.; having an instant, tactile hardware switch between IDE and non-IDE is almost as good as having double the monitor space!
If you're using OSX, I highly recommend Dash for managing local docs for all your programing languages, frameworks, and libraries - it's quiet extensive:
https://kapeli.com/dash
No affiliation, just a happy user :)
https://kapeli.com/dash
No affiliation, just a happy user :)
I used to use dash but found that just downloading websites works pretty well too
Tangential, but Dev Docs is a PWA that lets you save docs from major languages and frameworks for offline viewing:
https://devdocs.io/
Have you actually tried working on a laptop on an airplane? At least for me, it's a horrible experience - there's not enough space to use my laptop functionally.
Instead, if I want to feel productive, I'll focus on reading saved books & articles about relevant topics. They can easily be downloaded/cached to your kindle or phone before flying.
I'll also have a notebook (or recently, paper + clipboard) to brainstorm and take notes - help organize my next actions, thoughts, plans, and software designs.
Instead, if I want to feel productive, I'll focus on reading saved books & articles about relevant topics. They can easily be downloaded/cached to your kindle or phone before flying.
I'll also have a notebook (or recently, paper + clipboard) to brainstorm and take notes - help organize my next actions, thoughts, plans, and software designs.
Ergonomically, it's not the best. But the lack of distractions from the internet, and being stuck in one place, is a huge productivity boost for me. When flying alone, I can often knock out a side project prototype in one flight.
I actually find plane flights are a great opportunity to read longer form writing or otherwise do unplugged things. (OK, I often have some downloaded videos as well.)
I find even writing text isn't worth it. Partly because of the experience using a laptop and partly because doing so requires me to make all sorts of notes about things I need to verify once I'm back online. Unless I have a real time crunch it's just not worth it.
I find even writing text isn't worth it. Partly because of the experience using a laptop and partly because doing so requires me to make all sorts of notes about things I need to verify once I'm back online. Unless I have a real time crunch it's just not worth it.
For a few years I did most of my side-project programming on the commuter bus. Ergonomics is horrible of course but it helps to turn of the trackpad and embrace the keyboard shortcuts.
Internet was spotty so I pretended to be competely offline... Devdocs.io + saved pdf prints of various pages for offline docs.
Even though it was only 2x30 minutes 5 days a week, quite a lot got done.
Internet was spotty so I pretended to be competely offline... Devdocs.io + saved pdf prints of various pages for offline docs.
Even though it was only 2x30 minutes 5 days a week, quite a lot got done.
This is true. Got a couple books with me, luckily.
YMMV but I found that programming is an activity I am not productive on a plane.
An activity where I am productive is more theoretical work. Sketching on a remarkable and looking at some mathy stuff was fine for me even on a plane.
An activity where I am productive is more theoretical work. Sketching on a remarkable and looking at some mathy stuff was fine for me even on a plane.
I've done it. Works okay-ish for certain projects. Helps if you have local copies of docs and any packages you'd need beforehand. And if you have a part of the project to work on that doesn't need the internet to test. Might help to write mocks or specs for stuff that talks to the internet while you actually have it, then use them to develop against when you don't have it.
On the other hand, it may be more trouble than it's worth to arrange. Are you actually spending more than a few hours a month on flights? That's really not that much time, if it's much of a challenge to be productive then, maybe just let those few hours go and read a book or something.
On the other hand, it may be more trouble than it's worth to arrange. Are you actually spending more than a few hours a month on flights? That's really not that much time, if it's much of a challenge to be productive then, maybe just let those few hours go and read a book or something.
Look at where your arms are when you type and where your keyboard is in relation to your body. Then, imagine doing that on a plane, where your elbows generally have to stay tucked in and your keyboard is either on your tray table or resting on your thighs. Factor in the likelihood that the passenger in front of you will recline the seat back to rest during the flight.
Long story short, in six years of long-haul flights for work, I have never been productive on a laptop, aside from answering that one urgent email or running that one urgent remote command.
Long story short, in six years of long-haul flights for work, I have never been productive on a laptop, aside from answering that one urgent email or running that one urgent remote command.
Disconnect from the internet when you're home and work on your side projects. When you find you require a resource, connect and download it, then disconnect. Repeat until you have no need for an internet connection.
That's what I did and it works. It even lead to refactor the code to be more easily tested.
I also used this mini-tests mode to reshape the team for remote work in 2019: work one day remotely per week and see what breaks in our workflow and information/communication. Fix. Try again. Then work two days remotely and see what breaks. Then one week and see what breaks.
By the time COVID-19 started, I pulled the trigger in late February/early March: exclusively remote work and we were already set. My colleague canceled his rent contract and moved to another location and we did hit the road running because we had our mini-tests and fixed the most important workflow issues.
That's what I did and it works. It even lead to refactor the code to be more easily tested.
I also used this mini-tests mode to reshape the team for remote work in 2019: work one day remotely per week and see what breaks in our workflow and information/communication. Fix. Try again. Then work two days remotely and see what breaks. Then one week and see what breaks.
By the time COVID-19 started, I pulled the trigger in late February/early March: exclusively remote work and we were already set. My colleague canceled his rent contract and moved to another location and we did hit the road running because we had our mini-tests and fixed the most important workflow issues.
Reminds me of Bill Gates’ infamous “I wrote FAT on an airplane!” line :-)
When I still flew a lot (few times per month, EU to Asia and US) I had GPD Pocket 1 always with me. With Linux/i3 it had 15 hours battery and was perfectly fine in small spaces for building whatever I needed to build.
Anyone have any quick sites from which I can download, while I am at the airport, some projects/problems to work on while I am on the airplane, and internet may be unavailable or bad?
Might be a cool idea to make a site with discrete projects/problem sets specifically designed to be done without access to the internet.