Urgent.News

What's breaking now, across thousands of outlets.

Tech

Brain Frizz, Part 1: Blocking My Day

Brain Frizz, Part 1: Blocking My Day I review a lot of pull requests (PRs) now. Some of that is the job. As a staff engineer, part of my work is helping other people get unstuck, and on a team where AI agents write a lot of the code, what's usually stuck is a PR waiting on a review. The rest of my day goes to my own tickets, which usually means a few agent sessions running at once. Between the…

I spend a significant portion of my workday reviewing pull requests (PRs). A staff engineer's role often involves assisting others in getting unblocked, which frequently leads to multiple AI agent sessions running concurrently. As a result, I experience a condition I call "brain frizz" - a foggy, headache-inducing feeling that impairs concentration.

The tension in my shoulders increases, and I become more irritable. This phenomenon peaked on November 6th, so I devised an experiment to split my day into fixed blocks dedicated to specific tasks. This post outlines my plan and serves as a halfway point analysis, with the final results scheduled for publication on the 24th. My calendar reveals that meetings typically occur between 10:30 and 12:30, leaving afternoons largely unoccupied.

I structured my day around this pattern, allocating a morning block for ticket work, an afternoon for review meetings, and dedicated review blocks in the early afternoon and late afternoon. These blocks are recurring events on my calendar, reinforced through communication within the team. Despite the team's understanding, they often disregard the schedule when sending Slack messages or posting review requests in a shared channel.

Urgent review requests that could impact a deployment or a teammate's ability to progress are exceptions that can interrupt a ticket block. I track my brain frizz levels twice daily - once before the first ticket block and again at the end of the day. I assess my level of fog, headache, shoulder tightness, irritability, and the extent to which work from the previous day has carried over.

The primary focus of my tracking is the frequency of broken blocks, which occur when review requests or other interruptions disrupt my planned schedule. My success criteria for this experiment hinge on a measurable improvement in my brain frizz levels during the second week compared to my baseline score from November 10th. Specifically, my average fog score should decrease by at least half a point, with no more than two days registering a score of 4 or 5.

Failure would be defined as no improvement in brain frizz or increased delays in providing reviews due to the imposed blocks. As of the halfway point, I have not yet integrated the log tracking into my daily routine, but I am committed to starting from today onwards. Initial observations suggest that implementing the blocks has led to an improvement in my overall well-being, even if the data from the log tracking has not been documented.

I have noticed a shift in conversations amongst my colleagues, with many expressing similar challenges and proposing various solutions, including leveraging AI tools to optimize their attention management and adopting block scheduling for their own work. While these suggestions are valuable, the effectiveness of any solution ultimately depends on the individual's unique workflow and preferences.

I acknowledge that my proposed schedule may not be universally applicable and encourage readers to explore alternatives that better suit their individual needs. The final results and analysis will be published following the conclusion of the 24th day of the experiment.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Una estrategia de backup NoSQL necesita automatización y ensayos de recuperación

Autora: Adriana Rafaela Laos Gonzales Equipo: Antony Piero Solorzano Zegarra y Adriana Rafaela Laos Gonzales. Una estrategia de respaldo debe responder qué información protege, cuánto podría perderse…

  • Effective NoSQL backup strategy requires automation and recovery testing
  • Backup copy of Firestore-based task app retained for at least 24 hours, daily execution
  • Backup process involves temporary token, document querying, encryption, and artifact storage

The BIGINT Problem Explained

What Happens When Your Database Reaches 1 TB? How a growing events platform like Matoo helps us understand database limits, performance challenges, and the need to plan for scale.

  • BIGINT(20) supports up to 9.2 quintillion values, unlikely to be exhausted through normal use.
  • Indexes improve data retrieval efficiency but add storage overhead as database grows.

One clip-path doubled my browser cat's CPU cost in Chrome's GPU process

I made Tabloaf , a pixel cat for Chrome and Firefox. It walks across whatever page you have open, sits on pictures and headings, and chases a ball of yarn.

  • Chrome's GPU process increased from 15-17% to around 7% due to clip-path feature
  • Firefox's page process dropped from 19-20% to approximately 2% after optimizations
  • Optimized Tabloaf maintained consistent 17.5 ms frame time with no frame exceeding 20 ms

pdfjs-dist standard_fonts Missing in Next.js standalone

The short version pdfjs-dist's standard_fonts/ is read in a way Next.js file tracing cannot follow, so it can go missing from an output: "standalone" build. The effect of the omission is quiet.

  • pdfjs-dist missing standardfonts in Next.js standalone build
  • Causes text extraction from PDFs to break without exception
  • Explicitly state standardfonts in Next.js config to resolve

More from Thursday 19 November →