↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

I Got My Programming Time Back And So Can You

The author compares their remote work routine with a month spent in the office and notices a sharp drop in time spent programming, from about 25 hours a week down to around 17. Office life brought more meetings and scattered blocks of time that prevented getting into a sustained flow. Short gaps between meetings often turned into unproductive stretches spent on social media or extending lunch, based on the belief that no real work could be done before the next interruption.

Reflecting on why remote work in Berlin felt so productive, the author suspects that long, uninterrupted early‑morning stretches are the main factor. They test this by restructuring their office schedule to include two two‑hour protected coding blocks each day. Meeting availability is confined mostly to times people dislike for meetings, which subtly discourages unnecessary invitations. The change restores their weekly coding time and sense of contribution, though they remain cautious about possible downsides, such as reduced cross‑team communication. They close by imagining organizations that guarantee a daily no‑meeting focus window to balance collaboration with deep work.

Reading notes
#

  • While working remotely from Berlin, the author averaged about 25 hours per week on activities they classify as programming, tracked using RescueTime.
  • During the first three weeks in the San Francisco office, their programming time dropped to around 17 hours per week, and their perceived productivity fell by at least half.
  • The office schedule included multiple daily meetings plus lunch and special events, producing a fragmented day with frequent context switching.
  • The author identifies as a flow‑oriented programmer who works best with stretches of roughly two hours, where the most valuable work happens in the second hour.
  • Short intervals between meetings, such as 30 minutes after lunch, were often spent on Twitter, Feedly, or extended lunches, driven by the assumption that meaningful work could not start in that window.
  • They realize that high productivity while in Berlin may stem from having about four uninterrupted hours of focused work while others are asleep.
  • To test this idea, they redesign their day by blocking two separate two‑hour chunks specifically for focused work.
  • The revised schedule still leaves roughly four hours each day available for meetings, concentrated at 9am, during lunch, and at 4pm.
  • The author treats these time choices as a nudge that increases the perceived cost of inviting them to meetings, since most people dislike meetings at those times.
  • They reason that when their time appears freely available on the calendar, it is more likely to be consumed by meetings that reduce focused work.
  • After adopting the new schedule, their productive coding time returns to about 25 hours per week, and they again feel they are contributing at their usual level.
  • Feeling productive is described as a major source of joy in their work, and leaving a day without a sense of achievement is emotionally discouraging.
  • A possible downside is attending fewer meetings, which might eventually harm communication within the team and across teams.
  • The author watches for negative effects in team retrospectives and is open to adjusting the experiment if communication problems appear.
  • So far, they have not noticed any clear problems resulting from this scheduling change.
  • They mention companies that have adopted no‑meeting days and propose an alternative of daily no‑meeting time blocks.
  • The author imagines the benefit of knowing there is a guaranteed two‑hour period each day reserved for focused work.
  • They suggest that while collaboration and meetings are valuable, they can reach diminishing returns and need cultural adjustments to reduce their cost.
  • The author expresses interest in hearing about companies that experiment with cultural changes to maximize collaborative benefits while minimizing lost focus.