DEV Community: Brain Brutalism

Delete Your Backlog

Brain Brutalism — Fri, 21 Aug 2026 21:50:25 +0000

Your backlog is not inventory. It's debt.

Inventory is something you own and will use. Debt is an obligation that compounds whether you touch it or not. Every ticket you file, every "someday" feature, every non-critical bug — you tell yourself you're capturing value. You're not. You're signing a loan against your future attention, and the interest is paid in guilt every time you open the board.

That's backlog bankruptcy: the moment you admit the list will never be paid down, and stop pretending otherwise.

Built to grow

A list assumes completion. You work it, you finish it. A backlog assumes the opposite — it's built to grow faster than you can clear it. New ideas arrive daily. Old ones rot in place. The ratio only moves one direction.

So you triage. You re-rank. You "groom." None of that ships anything. It's an interest payment — the work you do to keep the debt looking manageable, which produces nothing except the sensation of being on top of it. That sensation is the trap: looking organized replacing being effective.

This is an excerpt. Read the rest at brainbrutalism.com.

Monk Mode: A Guide

Brain Brutalism — Fri, 21 Aug 2026 21:45:22 +0000

Monk Mode is not a productivity hack. It's a lifestyle design choice. It is the conscious decision to withdraw from the noise of the world to focus on your craft.

The Protocol:

Time Block: 8:00 AM - 12:00 PM. Non-negotiable.
Environment: Phone in another room. Wifi off (if possible). Door locked.
No Inputs: No email, no news, no social media before the block.
Single Output: Pick one big task. Do not switch.

I use a script to put my Mac into 'Monk Mode'. It kills all communication apps, turns on Do Not Disturb, and blocks time-wasting sites at the DNS level. When I'm in Monk Mode, I don't exist to the world. And that's exactly why I can create value for it.

This is an excerpt. Read the rest at brainbrutalism.com.

The Empty Desktop Policy

Brain Brutalism — Fri, 21 Aug 2026 21:40:14 +0000

Show me your desktop, and I'll tell you how you code. A cluttered desktop is a symptom of a cluttered mind. It represents deferred decisions. "I'll save this here for now." "I'll deal with this later."

Entropy is the default state of the universe. Keeping your digital environment clean requires active energy. It requires a system.

We instituted an 'Empty Desktop Policy'. At the end of every day, your desktop must be empty. Archive it, delete it, or process it. But do not leave it. This simple habit triggers a mindset of completion. It forces you to close loops. And that mindset transfers directly to your codebase.

This is an excerpt. Read the rest at brainbrutalism.com.

Why I Banned Slack on My Team

Brain Brutalism — Fri, 21 Aug 2026 21:35:02 +0000

Real-time chat is the enemy of deep work. A channel that expects an answer in minutes turns every engineer into a monitor — one eye always on the unread badge. That's not collaboration — it's a context switch your brain pays for every few minutes, and you can't solve a hard problem inside it.

So, leading an engineering team, I did the unthinkable. I banned Slack.

We went fully async. Documentation first. Long-form writing. Code comments. Pull request descriptions that actually explain the decision. The rule was simple: if it's urgent, call. If it's not, write it down and wait.

What I actually measured

A claim like "3x more deep work" is worthless without a definition of deep work. So we defined it before we changed anything, and measured the same way for six months on either side of the switch.

We called the unit a Focus Block Hour (FBH): a continuous block of at least 90 minutes, no meetings, fewer than two interruptions, with verifiable technical output at the end. Measured at the team level, in aggregate — no screenshots, no keylogging, no per-person surveillance. You don't need to spy on people to count whether the conditions for focus existed. You need an honest definition and the discipline to apply it.

This is an excerpt. The full teardown is at brainbrutalism.com.

Your Brain Is Not a Browser With 47 Tabs

Brain Brutalism — Fri, 21 Aug 2026 21:19:40 +0000

We treat multitasking as a skill. Job descriptions ask for it. We wear it like a badge. And somewhere along the way, someone told you the price: multitasking lowers your IQ. It makes you dumber. You've seen the stat. You may have quoted it.

It's junk.

The stat you've been quoting is junk science

The "multitasking drops your IQ" figure traces to a single 2005 experiment run for Hewlett-Packard by psychologist Glenn Wilson — eight participants, never peer-reviewed, released as a PR press note and nothing more. The media inflated it into neuroscience. Wilson himself later disowned it, saying it proved next to nothing. And what it measured wasn't a loss of IQ — it was temporary distraction while phones buzzed and email pinged. Switch the noise off and the "lost points" come back.

So no, multitasking isn't quietly lowering your IQ.

The real finding is worse.

This is an excerpt. Read the rest at brainbrutalism.com.

AI Onboarding Is Addiction Onboarding

Brain Brutalism — Fri, 21 Aug 2026 21:14:39 +0000

You're rolling out AI to your engineering team. Good intentions. You want them to move faster, ship more, spend less time on repetitive work.

What nobody put in the commercial proposal is the conflict of interest sitting at the centre of every tool you're signing off on.

The business model nobody explains

Generative AI tools bill by tokens. More queries, longer responses, more open conversations — more revenue. The economic incentive of these companies is directly aligned with the amount of time your engineers spend inside the tool.

That is not neutral.

A hammer has no opinion about how many nails you drive. A large language model has a recommendation system, follow-up suggestions, responses engineered to generate the next query. The difference isn't technical — it's intentional design.

When ChatGPT ends a response with "would you like me to go deeper on any of these points?", that's not helpfulness. That's retention.

This is an excerpt. Read the rest at brainbrutalism.com.

Constraint Decay: Why More Process Kills Your Team

Brain Brutalism — Fri, 21 Aug 2026 21:09:38 +0000

Your team isn't slow. It's buried under layers of process nobody questioned. Every methodology, every recurring meeting, every checklist felt reasonable the day it was added — and that's exactly why too much process is so hard to see. None of them is the problem. The accumulation is.

I call it constraint decay. Once you see it, you can't unsee it.

The problem: too much process, not too little

Most teams meet friction by adding structure. A process for this. A convention for that. A template, a ritual, a sign-off. Each new rule looks like control.

It isn't free.

Every rule you add taxes every future decision. It has to be remembered, satisfied, and reconciled with all the others already in place. That tax is paid in the scarcest resource a team has: decision cycles. The cost is invisible at first. The system absorbs it. People adapt. Throughput holds.

Until it doesn't.

This is an excerpt. The full teardown — complexity scorecard, data, and the BBM-approved alternative — is at brainbrutalism.com.

Meeting Consolidation Playbook: From 12 Meetings/Week to 4

Brain Brutalism — Fri, 21 Aug 2026 21:04:37 +0000

The Hybrid Day gives you a protected maker morning. But even the best schedule fails if the manager half of your day is a meeting death spiral. Your calendar fills because each meeting was defensible in isolation. None is the problem. The accumulation is. Same physics as constraint decay: each ritual seems reasonable when added, and together they consume everything.

I tracked my calendar for 6 months across four SaaS products. At my worst: 12 recurring meetings per week. Plus ad-hoc. Plus the "quick syncs." The week had 40 working hours. Meetings consumed 22 of them. The remaining 18 were fragmented into chunks too small for real work.

The fix wasn't declining individual meetings. It was redesigning the meeting system.

The meeting taxonomy

Most meetings fall into one of three categories. The first category you keep. The others you kill.

Category 1: Decisions (KEEP)

These meetings exist to make a specific decision that writing can't resolve. They have an agenda, a decision owner, and a timeout. If the decision isn't made in 30 minutes, it's deferred — not continued.

→ Architecture review with a hard call to make
→ Budget approval for a sprint
→ Product direction decision with disagreeing stakeholders

Max 2 per week. Non-negotiable timebox: 30 minutes.

Category 2: Status (KILL)

This is an excerpt. The full teardown is at brainbrutalism.com.

The 90-Minute Block: Deep Work Session Structure for Interrupted Environments

Brain Brutalism — Fri, 21 Aug 2026 20:59:36 +0000

The Hybrid Day gives you 5 hours of protected maker time. The async blueprint kills the interruptions that used to destroy it. But neither helps if you sit down with 5 open hours and spend 40 minutes deciding what to work on.

In a role that never stops pulling at your attention, deep work is not a matter of willpower. It's a matter of structure. The 90-minute block is that structure — a repeatable protocol for entering, sustaining, and exiting deep work in an environment designed to prevent it.

I've run this protocol daily for 18 months across four SaaS platforms. It works because it removes every decision except the work itself. You don't decide when to start. You don't decide when to break. You don't decide what to work on. The protocol decides. You execute.

Why 90 minutes

Every deep work framework picks a number. 52 minutes. 120 minutes. The Pomodoro 25. The exact number matters less than the principle: your brain has a finite attention budget per session, and attempting to exceed it yields diminishing returns.

I settled on 90 minutes for a specific reason. It's long enough to enter a genuine flow state — research suggests 10-23 minutes to achieve cognitive immersion after distraction. Below 90, you spend too much of the session getting into state and too little producing.

This is an excerpt. The full teardown is at brainbrutalism.com.

The Async Communication Blueprint: Team Protocols That Kill Interruptions

Brain Brutalism — Fri, 21 Aug 2026 20:54:35 +0000

Every team claims to be async. Most are just asynchronous SLA violations punctuated by meetings.

Async is not "we use Slack instead of meetings." Async is a documented protocol for every communication channel your team uses. It defines what goes where, when it gets answered, and how to escalate when something actually burns. Without those rules, async is just an excuse for ignoring messages until someone calls you.

I run four engineering teams on async protocols. Zero Slack notifications. Zero daily standups. And my response time on urgent issues is faster than it was when I had notifications on — because the signal-to-noise ratio inverted. Every ping is a legitimate escalation. Not a brain cell tax.

The three zones of communication

Every message belongs to one of three zones. The zone determines the tool, the expected response time, and the behavior.

Zone 1: Asynchronous (response within 4-24 hours)

This is where nearly all communication lives. 95% of messages belong here.

Tool	What goes here	Expected response
Linear / Jira	Tickets, task questions, code review requests	4 hours during working hours
Email	External communication, non-urgent internal	End of business day
Pull requests	Code reviews, technical decisions	4 hours during maker time
Shared docs	Proposals, design documents, strategy memos	24 hours for final feedback

This is an excerpt. The full teardown is at brainbrutalism.com.

The Hybrid Day: Schedule Templates for CTOs Who Code and Lead

Brain Brutalism — Fri, 21 Aug 2026 20:49:35 +0000

Every "time blocking for CTOs" article follows the same script. Wake up early. Block your calendar. Protect your deep work. Close with a quote from someone who doesn't ship software.

It works until the first production incident. Usually before 10am.

I manage four SaaS platforms. I write architecture decisions and review code. I also do the meetings, the hiring, the strategy, the investor calls. The advice to "just block time" fails because it assumes a stable day — and a CTO's day is never stable. The incident that kills your deep block isn't a failure of discipline. It's a failure of design.

The Hybrid Day is the fix.

The problem with single-mode blocking

Pure maker days assume you have no management responsibilities. Pure manager days assume you never touch code. Both assumptions are luxuries most CTOs can't afford.

The real constraint is cognitive. Coding requires a different mental state than meetings. The switch between them costs 15-23 minutes of recovery — documented in the same context-switch research I covered before. Every time you jump from a code review to a standup to a PR comment, you pay that cost. By 2pm you've context-switched six times and produced nothing of substance.

The solution isn't more willpower. It's a schedule that groups cognitive modes so you switch once, not a dozen times.

This is an excerpt. The full teardown is at brainbrutalism.com.

Why Not to Use Evernote

Brain Brutalism — Fri, 21 Aug 2026 20:44:34 +0000

Evernote was the future of note-taking. Then the future became a graveyard of abandoned notes you can never leave.

I understand why people stay. Evernote has been around since 2008. It holds 10+ years of accumulated thinking. It has notebooks and tags and web clipper integration and document scanning. Leaving feels like abandoning a part of your brain.

But here is the question nobody wants to ask: when was the last time Evernote made you better at your job?

The Promise vs The Reality

The promise: your external brain. Everything you see, read, and think — captured, organized, searchable, forever.

The reality: a dumping ground where notes go to die in nested notebooks with inconsistent tagging.

Evernote's problem is that it optimizes for capture, not retrieval. It makes it trivially easy to save anything — a web page, a PDF, a photo of a whiteboard, an audio recording. It makes it genuinely difficult to find anything later, because "search" is the only retrieval mechanism and search is only as good as your memory of what you saved.

I have spoken to dozens of former Evernote power users. Every single one described the same arc: enthusiastic capture, gradual accumulation, eventual abandonment. The notes are still there. Nobody reads them.

This is an excerpt. The full teardown — complexity scorecard, data, and the BBM-approved alternative — is at brainbrutalism.com.