Unpopular Opinion: I stopped coding on weekends and my career got better

NorthernDev spent years feeling guilty every Saturday morning, convinced real developers grind through the weekend. He logged 50 hours at his job and another 15 on side projects that never shipped anything anyone used. His Monday code got sloppy and his patience in meetings ran thin. About a year ago he set a hard boundary: laptop closes Friday at 5pm, doesn’t open again until Monday at 9am, no exceptions, including not checking pull requests.

He feared his skills would stagnate. Instead, problems started resolving themselves while he was away from the keyboard, hiking or washing dishes, and Monday mornings got noticeably faster. He also became easier to work with, less burned out and more patient in architecture meetings, and ties that shift to the promotion that followed.

Fichamento

#

• Years of guilt came from an industry ethos that equates passion with hours logged on nights and weekends.
• Before the change: 50-hour work weeks plus 15 weekend hours on side projects that went nowhere, leaving him exhausted and sloppy by Monday.
• The rule he set: laptop closed from Friday 5pm to Monday 9am, with no exceptions.
• Time away let problems resolve subconsciously; he solved Monday-morning issues in about 30 minutes that used to take 8 tired weekend hours.
• Being less burned out made him a better colleague, which he ties directly to getting promoted.
• Scarcity restored his appetite for coding instead of dreading it.
• He excludes two groups from the advice: developers who code on weekends purely because they enjoy it, and juniors who still need extra hours to close the knowledge gap early in their careers.
• He frames the advice for mid-level and senior developers stuck in hustle mode as permission to rest, since people need it to solve problems with code.