I wrote a bit about it in another reply[0]. - Disconnect from the internet - Unplug your laptop from the charger, or go somewhere else See how much work you

I wrote a bit about it in another reply[0]. - Disconnect from the internet - Unplug your laptop from the charger, or go somewhere else See how much work you can get done on a single laptop charge, without internet. No commute these days? Leave your charger in another room and start working. Once you get in the zone, you'll find it hard to leave to get your charger, similar to how you delay going to the bathroom when watching a movie, even though you could just hit pause. You'll be surprised. By the time your laptop's battery is at 6% or 5% you'll be slaying dragons. This is extremely useful when you want to implement a feature or fix a bug and you've been dragging your feet. The code doesn't need to be great, but you'll often have a prototype/proof of concept with the rightish abstraction, which you've been dragging your feet on. Some of my most effective work was done on a bus: "Come what may, I have 40 minutes to solve this issue". When I did it twice a day, that's a lot of issues taken off the backlog. It also works with learning something you've been delaying. "I have 40 minutes to go through this tutorial on Kubernetes/Docker". I won't learn all the subtleties, but it does work. Call it Bus/car Driven Development, or Battery Driven Development. Basically introducing a hard, physical, constraint that is a bit more real than a pomodoro timer. You actually have to get off the bus/car, or the laptop actually dies. It's more exciting than an alarm going off. - [0]: https://news.ycombinator.com/item?id=23547259 https://news.ycombinator.com/item?id=23547259