Some of the best and more useful code I wrote was during commute (though in a bus). I know I'm in there uninterrupted for one block of time. I know my battery w

Some of the best and more useful code I wrote was during commute (though in a bus). I know I'm in there uninterrupted for one block of time. I know my battery will only last for 2 hours. It speeds things up. That's also a tip I give to people to speed things up when they're home or at the office: disconnect from the internet, unplug from the charger, race to deliver a feature purely on battery. You won't be distracted by going into a rabbit hole of docs and browser tabs. You won't bother with premature optimisation and searching the internet for a better or the best way to do it. You just implement the first version of the deliverable with what you have, and then improve it. It also shows you what documents you really need. You'll want to have access to the docs offline for example. You don't have them? Next time. I had a project where some parts couldn't work without internet and working without internet pushed me to improve the code and make it more testable (dependency injection, mocks and stubs, etc)