The author finds themselves juggling a busy schedule in New York City, leading to less time for side projects. Their 30-minute subway commute, while seemingly manageable, eats up an hour each day. Instead of viewing this as wasted time, they've opted to use it for programming. Without the usual distractions of multiple monitors and internet access, they appreciate the focused environment. Free WiFi at some subway stops allows for brief internet access when necessary, but much of their work involves low-level embedded code that can only be compiled, not tested, during the commute. The subway's chaotic environment poses challenges. Complex tasks can be difficult to manage due to potential distractions, but the author finds that most programming tasks are more about busywork than deep focus. For particularly complex problems, they sketch diagrams in a small notebook. While they acknowledge the risk of theft, their inexpensive ThinkPad seems less appealing to potential thieves. The author has also enjoyed engaging conversations with strangers about their work, turning their odd habit into a way to connect with others. Finding a seat during rush hour is a major hurdle. The author expresses frustration when excitement for a project is thwarted by the lack of available seating. They are experimenting with a split keyboard attachment to allow programming while standing, paired with a screen-equipped pair of glasses. Despite the quirks, they encourage others to try programming on the subway, suggesting that building resilience to distractions can enhance productivity in other settings.