<h1>Do Not Write with an LLM</h1>
<img src="/images/green_bird.webp" alt="A photo taken by myself of a green bird.">
<h2>A Growing Trend</h2>
<p>I have been seeing an increasingly prevalent trend of people showing up in online spaces proudly flaunting that they are writing with the assistance of AI.
I often see them clarify that they are going further than letting the model perform grammar or fact-checking.
They are describing an idea to an LLM, and giving it complete control over the final written document.
They seem to be proud of this. They shouldn't be.</p>
<h2>What <strong>Does Not</strong> Work</h2>
<p>Writing seems to be a shadow of a more fundamental and useful process we like to call "thinking".
There is a reason why LLMs, which are the closest thing we currently have to "software that thinks" is trained to think through writing.
It seems logical, then, that we can use this "software that writes" to help along our own thinking process, right? Wrong.</p>
<p>Writing is one of the most cerebral activities that humans do on a regular basis.
<a href="https://elijahpotter.dev/articles/why-i-talk-to-myself">I try to sit down and write about a complex topic at least once a week.</a>
There are a number of reasons I do that pertaining to my job in particular, but there are more generally applicable reasons that can apply to any profession.</p>
<p>When a mathematician needs to think critically about some theorem or proof, they often turn to a dry-erase board or a chalkboard.
The mathematician then writes in clear notation what they imagine the problem to look like in their heads.
From there, they can manipulate that notation until they reach their desired outcome.</p>
<p>The English language is extremely similar, with a key difference.
Mathematical notation is specifically designed for a narrow domain.
Natural languages, on the other hand, can be applied to any field.
By writing your idea down on paper (or in a Google Doc, it does not matter), you give it substance.
This substance can then be shaped iteratively towards a goal of some kind.</p>
<p>No great ideas were written down on the first try.
They started as a vague notion, and through writing and rewriting, they became something concrete and valuable.
You cannot dictate a vague notation to an LLM and expect it to spit out something tangibly valuable.
Any attempt to do so is lazy, and it will result in failure.
I have seen it in the wild, and frankly, it is a little embarrassing.</p>
<p><a href="https://ammil.industries/i-know-you-didnt-write-this/">This article</a> feels especially relevant today.</p>
<h2>What <strong>Does</strong> Work</h2>
<p>Using an LLM for research can be very effective.
Searches to ChatGPT or Perplexity can surface information faster than digging around in a book you read three months ago.
For lots of searches, these two sources have completely replaced Google and DuckDuckGo for me.</p>
<p>They're also quite excellent fact-checkers.
I've seen that plenty of folks have received quite good results by pasting their work into an LLM with an internet tool (like ChatGPT with Thinking enabled).</p>
<p>Finally, I've personally found that LLMs are quite good at finding places where I simply forgot to insert context.
Sometimes I forget to define a term or insert a relevant link.
Even small models like <code>gemma3n:e2b</code> can catch me.</p>
<h2>What <strong>You</strong> Should Be Doing</h2>
<p>When you need to communicate an idea in your head, sit down with a notepad and a keyboard and explain it.
I personally think you should use a grammar checker, since they are far less likely to impede your thought process, but if you need to, you can instruct ChatGPT to critique your work once it is finished.</p>
<p>If an idea deserves an audience, you're capable of writing it out yourself.
In the same vein, if you can vaguely describe it to ChatGPT, you can vaguely describe it to your intended audience.
Do yourself a favor and skip the middleman.</p>
<h2>What We Should Be Building</h2>
<p>Now, I'd like to enter the section where I talk specifically about what this all means for people who create tools for writers.
That includes both Harper and WordPress.</p>
<p>A tool that helps someone write is a tool that directly interfaces with how that person thinks.
That might include what they think about, but more concretely I am referring to the actual day-to-day process of thinking through complex ideas.
If you don't believe me, it's probably because you skipped ahead instead of reading this post from the beginning.</p>
<p>Most crucially, we cannot allow ourselves to build tools that dissuade people from expressing their ideas in the way they imagine.
This can take the form of friction, like building tools that are so cumbersome that one dreads to open them at the start of the workday.
This can also take the form of a tool that crushes or overwrites an author's core message.</p>
<p>A common complaint I hear about Grammarly (from people who have switched to Harper from Grammarly) is that it's too demanding. When they write prose in a creative or unusual fashion, their service often forces them back into a colder and more formal way of speaking.
We don't want to be like them.</p>
<p>For Harper, that means we need to be diverse in our training datasets and mindful of feedback from our users.
For WordPress, it means we need to encourage our LLM integrations to tread lightly and respectfully.
They need to accept when they're wrong.
Just as any good human should.</p>
<blockquote>
<p>Months after writing this post, I came across another.
Author Cynthia Dunlop gives <a href="https://writethatblog.substack.com/p/dev-reaction-to-ai-blog-posts">a great overview of how developers react to blog posts written by AI</a>.
I highly suggest you take a look if you have more time.</p>
</blockquote>

I have been seeing an increasingly prevalent trend of people showing up in online spaces flaunting that they are writing with the assistance of AI. They seem to be proud of this. They shouldn't be.

<p>I have been seeing an increasingly prevalent trend of people showing up in online spaces flaunting that they are writing with the assistance of AI. They seem to be proud of this. They shouldn't be.</p>

Do Not Write with an LLM

<h1>Why I Talk to Myself</h1>
<img src="/images/bike_sidewalk.webp" alt="My bike broke down. Luckily, I had my camera">
<p>Each week I sit down and reflect on what I've learned. I think about which of my efforts have helped the Harper endeavor, and which have harmed it. It's not easy, but I think it's one of the best habits I've built. More accurately, it's one of the best habits <a href="https://ma.tt">Matt</a> has encouraged me to build.</p>
<p>When I really think about it, I'm reminded of the original <a href="https://blog.afterthedeadline.com/">After the Deadline blog</a>, which coincidentally also had a category called "Talking to Myself". I wonder if Raphael Mudge (AtD's author) had a similar motivation.</p>
<p>I talk to myself to find the weaknesses in Harper's mission and focus my attention on what matters. It is an efficient way to get from <a href="https://ma.tt/2025/05/sharing-levels/">layer one to layer five</a>. It can help get other maintainers on the same page and build a body of knowledge that can be linked to from anywhere.</p>
<p>Not worrying about keeping information locked-down is one of the more beautiful parts of working in public. Open source code would be nothing without similarly open source knowledge. I talk to myself <em>online</em> so my users can understand my intentions.</p>
<p>In many senses, we are not unlike moths. We are drawn to the lights of distraction, hype, and procrastination. For me, setting up checkpoints to stop and reflect has been an effective deterrent from these lights. In fact, I think each minute for which I stop and think has paid itself back three times over in time savings. If I can better allocate my time and energy, I can avoid doing redundant work pursuing pointless goals.</p>
<h2>Bonus Points</h2>
<p>A <a href="./markov_chains_are_the_original_language_models">few</a> of my <a href="./local-first_software_is_easier_to_scale">articles</a> have become popular on sites like Hacker News and Reddit. We've gotten quite a few Harper installations from links on these articles. I would never rely on this kind of blogging as a source of advertising, but it is nice to see it help spread the word.</p>

It's not easy, but I think it's one of the best habits I've ever built.

<p>It's not easy, but I think it's one of the best habits I've ever built.</p>

Why I Talk to Myself

<h1>My Writing Environment As a Software Engineer</h1>
<blockquote>
<p><strong>TL;DR: <em>Get a good text editor, and get good at using it.
Keep a notepad by your side.
Find a quiet place to write.</em></strong></p>
</blockquote>
<p>Writing is one of life's greater joys.
It's a mental workout that often brings me a level of clarity that is hard to find elsewhere.
I have never sat down to write for an extended period of time without coming away with a greater understanding of myself and the universe.</p>
<p>I imagine that sounds pretty cheesy.</p>
<p>I just want to impress upon you the importance writing has had in my life.
As with anything this important, I have an instinctual urge to optimize it.
As software engineers, isn't that part of our modus operandi?
To spend an unnecessary amount of time optimizing things?</p>
<p>Well, that's exactly what I've done.
Over the years, I've spend a unruly amount of time tweaking and changing the tools I use to write.
I'd love to talk about 'em.</p>
<h2>Neovim</h2>
<p>In the past few years, Neovim has the talk of the town.
Its ancestor, <code>vi</code> was borne from the observation that most writing is re-writing, and thus it includes a vast array of specific tools for editing text, rather than writing it.
<a href="https://www.reddit.com/r/neovim/"><code>r/neovim</code></a> has swelled to more than 110 thousand weekly visitors and thousands of plugins and LSPs to choose from.</p>
<p>Unless you choose a pre-built distro like <a href="https://www.lazyvim.org/">LazyVim</a>, Neovim does very little out of the box.
It is through relentless customization that it becomes something truly powerful.
Beside the various keybindings in my config, the important plugins and tools that I use are:</p>
<h3><a href="https://writewithharper.com">Harper</a></h3>
<p>As I'm the chief maintainer, this one should be of no surprise.
Don't worry, I won't give you the marketing spiel.
I'll simply say that Harper is a grammar checker that happens to work exceptionally well in Neovim.</p>
<h3><a href="https://github.com/folke/zen-mode.nvim">Zen Mode</a></h3>
<img src="/images/zen_mode.png" alt="Zen Mode: Activated">
<p>Plain Neovim organizes each file to cover the maximum amount of space on-screen.
Practically, this means most of my text ends up on the left side, which can hurt my neck.
Zen mode restricts the width of the file and centers it on the screen.</p>
<h3><a href="./the_simplest_neovim_markdown_setup">Tatum</a></h3>
<img src="/images/tatum_screenshot.webp" alt="A screenshot of Tatum at work">
<p>Tatum is a small tool I wrote in a few hours that lets me live-preview my Markdown as HTML.
I won't repeat myself.
If you're curious about Tatum, check out my <a href="./the_simplest_neovim_markdown_setup">previous blog post.</a></p>
<h3>More Details</h3>
<p>If you're thirsty for <em>all</em> the details of my Neovim setup, take a quick look at the configuration code on <a href="https://github.com/elijah-potter/dots/tree/master/nvim">GitHub</a>.</p>
<h2>ReMarkable 2</h2>
<p>A few years ago, while I was still in school, I splurged and purchased a used Remarkable 2.
Even now, there is rarely a day that goes by where I don't use it.
Sure, everything it does could be easily approximated by paper.
On the other hand, the thin device saves my back whenever I have to travel and there's a certain joy that comes from using an e-ink device like this.</p>
<img src="/images/remarkable.jpeg" alt="A Recent Brainstorming Session on the ReMarkable">
<p>I mostly use it to read digital books and blog posts, but it's also come in handy for getting around writer's block.
Being forced to slow down and use my hand to write, rather than a keyboard, is quite helpful in some inexplicable way.</p>
<h2>A Quiet Space</h2>
<p>More important than any text editor, at least for me, is a quiet space.</p>
<p>As I said before, writing can take real cognitive effort.
A space with distracting noise can make it unnecessarily hard to get words on paper.
I've found local libraries or co-working spaces to be great places for quiet authorship.</p>
<p>Whatever you do, do not listen to music with words in it.
Even if it <em>feels</em> more productive, I retroactively find that it makes me less so.</p>
<h2>Conclusion</h2>
<p>There's probably some more important points I'm leaving out, but I definitely believe I've hit the big three.
For me, the most important parts of a good writing environment, as a software engineer, are my text editor, a notepad, and a quiet space.</p>

Writing is one of life's greater joys. It's a mental workout that often brings me a level of clarity that is hard to find elsewhere.

<p>Writing is one of life's greater joys. It's a mental workout that often brings me a level of clarity that is hard to find elsewhere.</p>

My Writing Environment as a Software Engineer

<h1>What Was Radical Speed Month?</h1>
<p>While I was looking back through my archive of posts on this blog, I realized that I never concretely defined what Radical Speed Month was.
I have talked about it a lot, but there is not any one spot I can point to and say "Look there! That's what RSM was!"</p>
<p>This page will fill that void.</p>
<p>I work at <a href="https://automattic.com/">Automattic</a>.
We run a lot of products and host many services.
I can almost guarantee that you have used our product at least once in your life.
There are few people left on Earth that have not.</p>
<p>We like to experiment with new ways of working.
Our leadership team is constantly trying new things and new ways to get ahead of our competition.
Radical Speed Month, otherwise known as RSM, was one of these experiments.</p>
<p>In short, Radical Speed Month was a month-long sprint where any and all available engineers were instructed to stop whatever they were doing and work on something, well, radical.
Something new.
Something interesting.
Something no one had ever seen before.</p>
<p>That was the only restriction, other than working in pairs.
Each engineer, including myself, found one other engineer to work with and they spent a month on a project of their own choosing.
It was a lot like the hackathons I competed in during my more youthful years.</p>
<p>For the interested, here is a list of links to some of the posts I made during or relating to RSM:</p>
<ul>
<li><a href="./building_a_harper_desktop_app">Announcing work on our RSM project.</a></li>
<li><a href="./product_product_product">Learning from an expert at product-oriented thinking.</a></li>
<li><a href="./a_quick_update_on_harper_desktop">A quick update on our RSM project.</a></li>
<li><a href="./good_agents">Thinking about what makes a good agent (in the LLM sense of the word).</a></li>
<li><a href="./wrapping_up_harper_desktop">Reflecting on the project at large.</a></li>
</ul>

Elijah Potter

What Was Radical Speed Month?

Comments

Other Stuff

Do Not Write with an LLM

Why I Talk to Myself

My Writing Environment as a Software Engineer