Earlier quoted context omitted.
This is an insane response to someone having their carefully written work casually bastardized by an LLM that rewrote the entire design spec without even being informed. The amount of institutional noise generated by such carelessness far exceeds whatever improvement in readability you could possibly imagine. Any criticism you could aim at the original text that you don't even have on hand (i.e. are completely specul…
I thought the reply was generally helpful. Something to consider about in my equally exacting wording as I share the same frustration as the original comment and this give me a framework to view possible issues with my own writing. I.E. You can't change what others will do, you can only change what you yourself do. In this case: Carefully crafted exacting documentation is being ignored = frustrating to me = can't cha…
Stop trying to engineer your way out of listening to people
211–220 of 305 posts
Re: Stop trying to engineer your way out of listening to people
#212Earlier quoted context omitted.
You're assuming malign motivations, I'm assuming misplaced ones. It seems more likely to me the manager tried to read it and struggled, then generated something of equivalent size or larger. I'm taking it the generated document passed around was actually at least as large as the one-pager, and hence entirely pointless to rephrase even with the malign motivations you're assuming. Since the poster here wears his person…
When I read documentation, I'm not there to enjoy the experience. I'm there to find out how the documented thing works and how to use it. It's not a novel. I'm not there for entertainment. Chasing readability without maintaining accuracy is a failure in the context of documentation no matter the motivations involved. I'm not saying that readability can't be a consideration when making documentation. I am saying that…
You're right to elevate accuracy to a high level of importance, but that is NOT ENOUGH if the thing is has poor readability. The audience has to be able to understand the document if the document is to be useable.
There's only a certain amount of effort anyone can deliver in producing a document. But if the author can't deliver readability, they need to follow up the document with a lot of support and/or get some help to make it useable.
Re: Stop trying to engineer your way out of listening to people
#213Earlier quoted context omitted.
>Writing has always been a great burden. It should not be elevated to, nor equivocated with, some great utility or intellectual practice. That was for an era where sound was harder to record and transmit than words; and where meetings required moving around the world. Okay Socrates[1]. Obviously writing has not been a "great burden" because it's 5000 years later and we're still all doing it. It hasn't been enough of…
So you prefer writing. Either way, writing is dying. It's dying because speaking and meeting can now be transmitted as easily. This itself should, empirically, demonstrate the point. The podcast killed the book, the meeting killed the memo. All around us writing is dying, and writing no one wants to read even more quickly. Soon, in my view, writing will be seen as an instrumental intermediate artefact for technical o…
Some AWS meetings require the memo.
> writing and reading was, and is, a great burden to many
Other terms for writing and reading:
• transmission
• thinking (@paulg essay)
• memory RL (reinforcement learning)
• advantage
• moat
> read more transcriptsTranscripts are primary sources. Sufficiently valuable primary sources can inspire new sources, created by humans through a process that includes, but is not limited to, reading and writing.
Re: Stop trying to engineer your way out of listening to people
#214Earlier quoted context omitted.
This is an insane response to someone having their carefully written work casually bastardized by an LLM that rewrote the entire design spec without even being informed. The amount of institutional noise generated by such carelessness far exceeds whatever improvement in readability you could possibly imagine. Any criticism you could aim at the original text that you don't even have on hand (i.e. are completely specul…
You're assuming malign motivations, I'm assuming misplaced ones. It seems more likely to me the manager tried to read it and struggled, then generated something of equivalent size or larger. I'm taking it the generated document passed around was actually at least as large as the one-pager, and hence entirely pointless to rephrase even with the malign motivations you're assuming. Since the poster here wears his person…
And in the process, you give zero benefit of the doubt to OP. You just assume he wrote it badly.
Re: Stop trying to engineer your way out of listening to people
#215Earlier quoted context omitted.
Perhaps you should ask the manager why he passed it through AI. It might be that with precision, readability is lost. It's a tradeoff: the more compressed your language is, and hence the more precise, the more cognitive effort you require the reader to expend on each word. Reading is a translation from your mental model, as expressed in words, to the readers mental model. Words alone don't perform this translation, t…
No. Someone replaced well thought out documentation with AI fabrications and let GP take the fall for it. That is malicious and inexcusable. It's not on GP, the fault lies with the idiot that ran gold documentation through the bullshit machine. Don't blame someone who was wronged, that makes you a malicious asshole.
But yes do be on the lookout for malicous people, document, log and look for patterns... don't write it off, document.
Re: Stop trying to engineer your way out of listening to people
#216Earlier quoted context omitted.
I can still see a path where the manager was stupid but not malicious. The manager sent on a document which he was too lazy to check at least had the right endpoints but left the GP's contact details on. I could also imagine intentional harm to GP's reputation was the goal, with really clumsy execution.
Either way, that person should not be managing anything. And if it was an honest mistake, they need to come out and apologize both to the IC and to the team that is using the documentation.
Re: Stop trying to engineer your way out of listening to people
#217Earlier quoted context omitted.
>Writing has always been a great burden. It should not be elevated to, nor equivocated with, some great utility or intellectual practice. That was for an era where sound was harder to record and transmit than words; and where meetings required moving around the world. Okay Socrates[1]. Obviously writing has not been a "great burden" because it's 5000 years later and we're still all doing it. It hasn't been enough of…
So you prefer writing. Either way, writing is dying. It's dying because speaking and meeting can now be transmitted as easily. This itself should, empirically, demonstrate the point. The podcast killed the book, the meeting killed the memo. All around us writing is dying, and writing no one wants to read even more quickly. Soon, in my view, writing will be seen as an instrumental intermediate artefact for technical o…
Re: Stop trying to engineer your way out of listening to people
#218I tend to be very exacting in my word choice. If I used a specific word, I meant it. Many people I find speak in what I would describe as tone poems. They circle around an idea using whatever word is within reach, and expect you to understand the meaning based on shared connotations. These people are tiring to interpret. When I write something, each and every word was chosen specifically and with intention. The numbe…
Or the birth of rigorous feedback loops.
Any message can be corrupted during transmission.
Feedback forms can diff received text against transmitted text.
Re: Stop trying to engineer your way out of listening to people
#219Even here in the comments you see people who have read this article and fall victim to the very things it’s pointing out. It’s ironic. Let me add a couple to this list. 1. No amount of knowledge or discussion will make a person accept something they don’t want to accept. 2. To truly listen means to place yourself mentally and physically in a vulnerable state. Because you will likely hear things that run contrary to y…
Discussion, probably not. Modifying incentive structures, absolutely.
Re: Stop trying to engineer your way out of listening to people
#220Earlier quoted context omitted.
So you prefer writing. Either way, writing is dying. It's dying because speaking and meeting can now be transmitted as easily. This itself should, empirically, demonstrate the point. The podcast killed the book, the meeting killed the memo. All around us writing is dying, and writing no one wants to read even more quickly. Soon, in my view, writing will be seen as an instrumental intermediate artefact for technical o…
Another way of looking at that is that if writing is dying then doing it well will become a key competitive advantage. Organizations with culture, processes, and hiring standards focused on effective written communication will be faster and more economically efficient than competitors that rely on meetings (or recordings of meetings). Really crisp writing is especially helpful when prompting an LLM.