<h1>Hacker News, sans AI</h1>
I like Hacker News, but I do not love that so much of it has turned into dis­cus­sion of a sin­gle topic: AI. So, I have cre­ated my own ver­sion.
A ver­sion of Hacker News, with­out AI.
<a href="/hnsansai">HNSansAI</a> pulls from the of­ﬁ­cial Hacker News API, looks through the con­tent of each ar­ti­cle, and dis­cards any that men­tion a term re­lated to “AI”. That in­cludes stuff like:
<ul>
<li>“OpenAI”</li>
<li>“Anthropic”</li>
<li>“Copilot”</li>
<li>“LLM”</li>
<li>…and many more.</li>
</ul>

I like HackerNews, but I don't love that so much of it has turned into discussion of a single topic: AI. This is a version of HackerNews, filtered to remove any article focusing on __AI__. Refreshes about every ten minutes.

I like HackerNews, but I don’t love that so much of it has turned into dis­cus­sion of a sin­gle topic: AI. This is a ver­sion of HackerNews, ﬁl­tered to re­move any ar­ti­cle fo­cus­ing on AI. Refreshes about every ten min­utes.

Hacker News sans AI

It didn't work for me, and if you reading this, it probably won't work for you either.

It did­n’t work for me, and if you read­ing this, it prob­a­bly won’t work for you ei­ther.

Do Not Type Your Notes

<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>
I have been see­ing an in­creas­ingly preva­lent trend of peo­ple show­ing up in on­line spaces proudly ﬂaunt­ing that they are writ­ing with the as­sis­tance of AI.
I of­ten see them clar­ify that they are go­ing fur­ther than let­ting the model per­form gram­mar or fact-check­ing.
They are de­scrib­ing an idea to an LLM, and giv­ing it com­plete con­trol over the ﬁ­nal writ­ten doc­u­ment.
They seem to be proud of this. They should­n’t be.
<h2>What Does Not Work</h2>
Writing seems to be a shadow of a more fun­da­men­tal and use­ful process we like to call “thinking”.
There is a rea­son why LLMs, which are the clos­est thing we cur­rently have to “software that thinks” is trained to think through writ­ing.
It seems log­i­cal, then, that we can use this “software that writes” to help along our own think­ing process, right? Wrong.
Writing is one of the most cere­bral ac­tiv­i­ties that hu­mans do on a reg­u­lar ba­sis.
<a href="https://elijahpotter.dev/articles/why-i-talk-to-myself">I try to sit down and write about a com­plex topic at least once a week.</a>
There are a num­ber of rea­sons I do that per­tain­ing to my job in par­tic­u­lar, but there are more gen­er­ally ap­plic­a­ble rea­sons that can ap­ply to any pro­fes­sion.
When a math­e­mati­cian needs to think crit­i­cally about some the­o­rem or proof, they of­ten turn to a dry-erase board or a chalk­board.
The math­e­mati­cian then writes in clear no­ta­tion what they imag­ine the prob­lem to look like in their heads.
From there, they can ma­nip­u­late that no­ta­tion un­til they reach their de­sired out­come.
The English lan­guage is ex­tremely sim­i­lar, with a key dif­fer­ence.
Math­e­mat­i­cal no­ta­tion is specif­i­cally de­signed for a nar­row do­main.
Nat­ural lan­guages, on the other hand, can be ap­plied to any ﬁeld.
By writ­ing your idea down on pa­per (or in a Google Doc, it does not mat­ter), you give it sub­stance.
This sub­stance can then be shaped it­er­a­tively to­wards a goal of some kind.
No great ideas were writ­ten down on the ﬁrst try.
They started as a vague no­tion, and through writ­ing and rewrit­ing, they be­came some­thing con­crete and valu­able.
You can­not dic­tate a vague no­ta­tion to an LLM and ex­pect it to spit out some­thing tan­gi­bly valu­able.
Any at­tempt to do so is lazy, and it will re­sult in fail­ure.
I have seen it in the wild, and frankly, it is a lit­tle em­bar­rass­ing.
<a href="https://ammil.industries/i-know-you-didnt-write-this/">This ar­ti­cle</a> feels es­pe­cially rel­e­vant to­day.
<h2>What Does Work</h2>
Using an LLM for re­search can be very ef­fec­tive.
Searches to ChatGPT or Perplexity can sur­face in­for­ma­tion faster than dig­ging around in a book you read three months ago.
For lots of searches, these two sources have com­pletely re­placed Google and DuckDuckGo for me.
They’re also quite ex­cel­lent fact-check­ers.
I’ve seen that plenty of folks have re­ceived quite good re­sults by past­ing their work into an LLM with an in­ter­net tool (like ChatGPT with Thinking en­abled).
Finally, I’ve per­son­ally found that LLMs are quite good at ﬁnd­ing places where I sim­ply for­got to in­sert con­text.
Some­times I for­get to de­ﬁne a term or in­sert a rel­e­vant link.
Even small mod­els like <code>gemma3n:e2b</code> can catch me.
<h2>What You Should Be Doing</h2>
When you need to com­mu­ni­cate an idea in your head, sit down with a notepad and a key­board and ex­plain it.
I per­son­ally think you should use a gram­mar checker, since they are far less likely to im­pede your thought process, but if you need to, you can in­struct ChatGPT to cri­tique your work once it is ﬁn­ished.
If an idea de­serves an au­di­ence, you’re ca­pa­ble of writ­ing it out your­self.
In the same vein, if you can vaguely de­scribe it to ChatGPT, you can vaguely de­scribe it to your in­tended au­di­ence.
Do your­self a fa­vor and skip the mid­dle­man.
<h2>What We Should Be Building</h2>
Now, I’d like to en­ter the sec­tion where I talk specif­i­cally about what this all means for peo­ple who cre­ate tools for writ­ers.
That in­cludes both Harper and WordPress.
A tool that helps some­one write is a tool that di­rectly in­ter­faces with how that per­son thinks.
That might in­clude what they think about, but more con­cretely I am re­fer­ring to the ac­tual day-to-day process of think­ing through com­plex ideas.
If you don’t be­lieve me, it’s prob­a­bly be­cause you skipped ahead in­stead of read­ing this post from the be­gin­ning.
Most cru­cially, we can­not al­low our­selves to build tools that dis­suade peo­ple from ex­press­ing their ideas in the way they imag­ine.
This can take the form of fric­tion, like build­ing tools that are so cum­ber­some that one dreads to open them at the start of the work­day.
This can also take the form of a tool that crushes or over­writes an au­thor’s core mes­sage.
A com­mon com­plaint I hear about Grammarly (from peo­ple who have switched to Harper from Grammarly) is that it’s too de­mand­ing. When they write prose in a cre­ative or un­usual fash­ion, their ser­vice of­ten forces them back into a colder and more for­mal way of speak­ing.
We don’t want to be like them.
For Harper, that means we need to be di­verse in our train­ing datasets and mind­ful of feed­back from our users.
For WordPress, it means we need to en­cour­age our LLM in­te­gra­tions to tread lightly and re­spect­fully.
They need to ac­cept when they’re wrong.
Just as any good hu­man should.
<blockquote>
Months af­ter writ­ing this post, I came across an­other.
Au­thor Cynthia Dunlop gives <a href="https://writethatblog.substack.com/p/dev-reaction-to-ai-blog-posts">a great overview of how de­vel­op­ers re­act to blog posts writ­ten by AI</a>.
I highly sug­gest you take a look if you have more time.
</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.

I have been see­ing an in­creas­ingly preva­lent trend of peo­ple show­ing up in on­line spaces ﬂaunt­ing that they are writ­ing with the as­sis­tance of AI. They seem to be proud of this. They should­n’t be.

Do Not Write with an LLM

<h1>Writing Good Documentation</h1>
I be­lieve that good doc­u­men­ta­tion is more im­por­tant than ever. In an age where large lan­guage mod­els have ex­cep­tional con­text win­dows, it’s easy to fall into the trap of be­liev­ing a sys­tem is sim­pler than it is. To test the lim­its of their abil­i­ties, I’ll of­ten feed Harper code in and ask for their ex­pla­na­tion of it’s in­ner work­ings.
They’ve never got­ten it any­where close to cor­rect.
That’s be­cause good doc­u­men­ta­tion is more than the sum of its parts. It should con­tain all the rel­e­vant tech­ni­cal de­tails needed to work on a repos­i­tory, but it should also pro­vide a sense of qual­ity and di­rec­tion. It should dis­till an abil­ity within the reader to tell what good code and con­duct looks like.
I think this is an area Harper could do to im­prove on.
<h2>It’s Possible to Write Too Much</h2>
Too much text can be over­whelm­ing.
I have met many peo­ple (myself in­cluded) who be­lieve that more de­tail is al­ways bet­ter.
That as long as the in­for­ma­tion ex­ists some­where, some­one will be able to ﬁnd it.
In re­al­ity, that’s just not true.
That brings us to our ﬁrst rule: good doc­u­men­ta­tion should be sim­ple.
The worst way to de­scribe a com­plex sys­tem is with com­plex lan­guage.
It’s much bet­ter to ﬁrst break it down into sim­pler parts.
From there, you can build it back up again.
I’ve found it ef­fec­tive to start by erring on the side of “too much”, only to pare it down later.
Needless to say, it’s also pos­si­ble to write too lit­tle.
<h2>Focus on Why</h2>
The code it­self is (or should be) the best de­scrip­tion of how the soft­ware works.
Doc­u­men­ta­tion should com­ple­ment this re­al­ity by de­scrib­ing why the soft­ware works that way.
This might in­clude a lit­tle his­tory.
What steps did the orig­i­nal code’s au­thor take be­fore ar­riv­ing on the ﬁ­nal so­lu­tion?
<a href="https://elijahpotter.dev/">A blog</a> is a great way to an­swer that ques­tion.
When de­scrib­ing a bug rel­e­vant to some code (like in a pull re­quest), a pic­ture is worth a thou­sand words.
It’s much eas­ier to show a prob­lem than to de­scribe it.
That’s why I highly sug­gest you take a screen­shot of the prob­lem.
Even bet­ter: record a video recre­ation of it.

In an age where large language models have exceptional context windows, it's easy to fall into the trap of believing a system is simpler than it is.

In an age where large lan­guage mod­els have ex­cep­tional con­text win­dows, it’s easy to fall into the trap of be­liev­ing a sys­tem is sim­pler than it is.

Elijah Potter

Writing Good Documentation

It’s Possible to Write Too Much

Focus on Why

Comments

Other Stuff

Hacker News sans AI

Do Not Type Your Notes

Do Not Write with an LLM