Commit `c417506d6b`

c417506d6b35454b57abdbd222043f11e779e793

parent: c92a790103

Verified · cmc

cmc <hello@cleberg.net> · 2026-05-13 19:41 UTC

fix: minor edits to latest post

Layout: unified · split

content/blog/2026-05-13-plain.org +4 −4

	@@ -116,7 +116,7 @@ make content harder to use.
116		116
117	Plain text gives you portability. It does not automatically give you clarity.	117	Plain text gives you portability. It does not automatically give you clarity.
118		118
119	A =README= can be written in Markdown and still fail to explain what the project	119	A README can be written in Markdown and still fail to explain what the project
120	does. A runbook can be stored in Git and still assume tribal knowledge. An audit	120	does. A runbook can be stored in Git and still assume tribal knowledge. An audit
121	workpaper can be easy to archive and still fail to explain the conclusion. A	121	workpaper can be easy to archive and still fail to explain the conclusion. A
122	policy can be available to every employee and still be written in a way that	122	policy can be available to every employee and still be written in a way that
	@@ -127,7 +127,7 @@ accessible technologically and yet, you get nothing out of it? You could re-read
127	it numerous times and never get an answer because the author was not focused on	127	it numerous times and never get an answer because the author was not focused on
128	accessible language.	128	accessible language.
129		129
130	The file is accessible, but the meaning is not, and that matters a lot. A	130	The file is accessible, but the meaning is not and that matters a lot. A
131	document is not useful because it exists in an open format. It is useful when	131	document is not useful because it exists in an open format. It is useful when
132	someone can read it, understand it, and act on it.	132	someone can read it, understand it, and act on it.
133		133
	@@ -190,10 +190,10 @@ good format. You can store unclear decisions in Markdown. You can preserve vague
190	notes forever. You can make a document technically accessible while leaving it	190	notes forever. You can make a document technically accessible while leaving it
191	practically unreadable.	191	practically unreadable.
192		192
193	(Have you ever read a README clearly written by AI without any editing from the	193	Have you ever read a README clearly written by AI without any editing from the
194	repository owner? It can quickly become nonsense as the AI tries to constrain	194	repository owner? It can quickly become nonsense as the AI tries to constrain
195	its content to the best possible README standard, while it loses any meaning of	195	its content to the best possible README standard, while it loses any meaning of
196	the project itself.)	196	the project itself.
197		197
198	That is why plain language belongs in the same conversation.	198	That is why plain language belongs in the same conversation.
199		199

Commit c417506d6b

Commit `c417506d6b`