Hacker News with Generative AI: Technical Writing

The Seven-Action Documentation Model (passo.uno)
I think all technical writers, at some point or another, feel the urge to base their work on something more systematic than “it’s just the way folks documented stuff since forever”. Toolkits and frameworks provide content types, which is immensely valuable when you know what you want to write, but starting from there is like buying a hammer without knowing that half of the work you’ll do is turning screws.
Oral History of Caroline Rose, Writer of Inside Macintosh (ycombinator.com)
Caroline Rose was a technical writer at Apple from 1982, lead writer and editor of "Inside Macintosh".
Myst Markdown – Markdown for technical/scientific document (mystmd.org)
MyST is an ecosystem of open-source, community-driven tools designed to revolutionize scientific communication.
Why your team needs a Technical Writer to manage your documentation (momorell.com)
Making Screenshots of Test Equipment Old and New (tomverbeure.github.io)
Last year, I create Fake Parallel Printer, a tool to capture the output of the parallel printer port of old-ish test equipment so that it can be converted into screenshots for blog posts etc.
Your docs are your infrastructure (stackoverflow.blog)
Fabrizio Ferri-Benedetti, who spent many years as a technical writer for Splunk and New Relic, joins Ben and Ryan for a conversation about the evolving role of documentation in software development.
Embeddings are underrated (technicalwriting.dev)
Machine learning (ML) has the potential to advance the state of the art in technical writing. No, I’m not talking about text generation models like Claude, Gemini, LLaMa, GPT, etc. The ML technology that might end up having the biggest impact on technical writing is embeddings.
What docs-as-code means (passo.uno)
I’ve recently started a new job as a documentation engineer. While my work is largely the same as that of a technical writer, the sound and semantics of my new job title gave me some pause and made me think about what it really means to be doing docs-as-code. To say that it’s about writing documentation using the same tools and methods as software developers is correct, but fails to acknowledge the full consequences of the fact.
Focus on decisions, not tasks (technicalwriting.dev)
In technical communication, we don’t talk much about decision support; we talk about task support… In many cases, the information people need to complete their tasks is not information on how to operate machines, but information to support their decision making… simply documenting the procedures is never enough… What I am talking about is documenting the context, letting users know what decisions they must make, making them aware of the consequences, and, as far as possible, leading them to resources
I Landed 4 Jobs and Earned $25K+ with Technical Writing (catalins.tech)
As a final-year university student preparing to enter the industry, I knew I had to differentiate myself from other candidates in a competitive job market. That's when the idea struck me: what if I combined two activities I enjoy, programming and writing?
LaTeX Style Guide for EE 364B [pdf] (2014) (web.stanford.edu)
Technical writing is too important to leave to language models (counting-stuff.com)
There are no shortcuts to writing something worth reading
Ask HN: Technical Writing Resources (ycombinator.com)
There is no mystery over who wrote the Blue Screen of Death (microsoft.com)
Contributing to open source docs as a technical writer (passo.uno)
You can deeplink to a specific PDF page (technicalwriting.dev)
You can deeplink to a specific PDF page (technicalwriting.dev)
Our guidance on using LLMs (for technical writing) (ritza.co)
Git Workflows for API Technical Writers (bump.sh)
The 'blem wit' error messages: Things get terse (2008) (theregister.com)
Simplified Technical English (asd-ste100.org)
What makes a great technical blog (eatonphil.com)