# Cognitive Burden

DevFeed: [Cognitive Burden](<https://devfeed.tech/articles/cognitive-burden-25232.md>)

Original publisher: [Read original article](<https://kau.sh/blog/cognitive-burden/>)

Author: Kaushik Gopal

Published: 2025-11-04T22:24:00Z

Content type: opinion

Language: en

Sources: [Kaushik Gopal's Site](<https://devfeed.tech/sources/kaushik-gopal-s-site.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [coding](<https://devfeed.tech/topics/coding.md>), [Requirements](<https://devfeed.tech/topics/requirements.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [coding](<https://devfeed.tech/tags/coding.md>), [llms](<https://devfeed.tech/tags/llms.md>), [recent-fervor](<https://devfeed.tech/tags/recent-fervor.md>), [requirements](<https://devfeed.tech/tags/requirements.md>)

## AI overview

The author argues that AI tools are valuable primarily because they reduce cognitive burden and tedious work, rather than because they are inherently faster. Examples include using a custom agent to draft writing from bullet points and using AI while managing multiple software features, with the author continuing to review the output.

## Source excerpt

A common argument I hear against AI tools: "It doesn't do the job better or faster than me, so why am I using this again?" Simple answer: cognitive burden. My biggest unlock with AI was realizing I could get more done, not because I was faster, but because I wasn't wringing my brain with needless tedium. Even if it took longer or needed more iterations, I'd finish less exhausted. That was the aha moment that sold me. On Writing # Simple example: when writing a technical1 post, I start with bullet points. Sometimes there's a turn of phrase or a bit of humor I enjoy, and I'll throw those in too. Then a custom agent trained on my writing generates a draft in my voice. After it drafts, I still review every single word. A naysayer might ask: "Well, if you're reviewing every single word anyway, at that point, why not just write the post from scratch?" Because it's dramatically easier and more enjoyable not to grind through and string together a bunch of prepositions to draft the whole post. I've captured the main points and added my creative touch; the AI handles the rest. With far less effort, I can publish more quickly -- not due to raw speed, but because it's low-touch and I focus only on what makes it uniquely me. Cognitive burden ↓. On Coding # About two years ago I pushed back on our CEO in a staff meeting: "Most of the time we engineers waste isn't in writing the code. It's the meetings, design discussions, working with PMs, fleshing out requirements -- that's where we should focus our AI efforts first."2 I missed the same point. Yes, I enjoy crafting every line of code and I'm not bogged down by that process per se, but there's a cognitive tax to pay. I'd even say I could still build a feature faster than some LLMs today (accounting for quality and iterations) before needing to take a break and recharge. Now I typically have 3-4 features in flight (with requisite docs, tests, and multiple variants to boot). Yes, I'm more productive. And sure, I'm probably shipping f