#TechnicalWriting

Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-05-25

"How to leverage documentation effectively in Cursor through prompting, external sources, and internal context

Why documentation matters

Documentation provides current, accurate context. Without it, models use outdated or incomplete training data. Documentation helps models understand things like:

- Current APIs and parameters
- Best practices
- Organization conventions
- Domain terminology

And much more. Read on to learn how to use documentation right in Cursor without having to context switch."

docs.cursor.com/guides/advance

#AI #GenerativeAI #Cursor #TechnicalWriting #Documentation #SoftwareDevelopment #APIDocumentation #SoftwareDocumentation

Dysmorphia💛🤍💜🖤dys_morphia@sfba.social
2025-05-23

Haunted manuals lightning talk

I gave a lightning #WriteTheDocs in Portland, and in this post I share the recording and my slide deck.

rinsemiddlebliss.com/posts/202

#TechnicalWriting

2025-05-22

'No docs, no bugs': simonwillison.net/2025/May/22/

The idea that test records will suffice as documentation *could* work for some users. Some potential customers, especially those working for governments and high-risk environments (for example, nuclear power plants) would probably reject the use of test records as documentation.

To me, this thinking sounds economical but is in fact not geared to the end user, unless the end user is exactly the same kind of people who perform tests. In my experience, testers are seldom the same as end users, even when it comes to very technical docs.

#TechnicalWriting #TechComm #docs

If your library doesn't have any documentation, it can't have any bugs.

Documentation specifies what your code is supposed to do. Your tests specify what it actually does.

Bugs exist when your test-enforced implementation fails to match the behavior described in your documentation. Without documentation a bug is just undefined behavior.
Anthony Deandtgeek
2025-05-20

I've tried getting writing related work (specifically technical writing) for years and it's ultimately not exactly been as successful as I'd like. (One reason I run my blog, as a writing outlet/show my skills.) Reading about writers getting hired while using AI isn't encouraging.

Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-05-19

"Your voice must be heard. Inside of your work, you need key stakeholders and teams to know what it is that you do and the value you bring to product development. Your docs are vital infrastructure, but folks won’t realize that until it’s too late. Unless, of course, you become an ambassador of your craft and start making yourself heard and present everywhere. One of the first things I did when I joined a startup was sending an email to the team telling them what I did. It became my first post.

Outside of work, this task is equally important, because tech writing has a depth issue. You must develop a sense of pride in technical communication as a vital discipline. Don’t shy away from intellectual engagement and contribute to the field by sharing your own thoughts, theories, and errors. Some career ladders label that as “thought leadership”. It’s really about showing up and owning the conversation around what we do and why it matters, moving beyond praxis to noesis."

passo.uno/how-to-grow-senior-t

#TechnicalWriting #TechnicalWriter #TechnicalCommunication #LifeLongLearning #SoftwareDocumentation #DocsAsInfrastructure

N-gated Hacker Newsngate
2025-05-12

🚨 BREAKING NEWS: , that ancient artifact from the dusty corners of ML, are apparently the unsung heroes of technical writing! 🤯 Who knew that connecting texts like a glorified game of connect-the-dots could revolutionize your mundane documentation? 💡 Thank you, Captain Obvious, for this revelation! 😂
technicalwriting.dev/ml/embedd

Rafael Perezrperezrosario
2025-05-08

8 Light writer Taylor Keazirian argues in favor of maintaining a set of "living" documents as part of software development project efforts. Common misconceptions about software documentation are addressed and refuted with insights on what a minimal technical set of documents for a software project should look like.

"Mastering Technical Documentation"

8thlight.com/insights/masterin

Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-05-08

"Welcome to the State of Docs Report 2025, bringing together insights from documentation experts from across the industry.

This comprehensive report explores how teams track their docs’ success, the future of the industry, the ongoing impact of AI on documentation, and much more.
(...)
We received responses from 444 hands-on documentation experts — including technical writers, managers, engineers, support teams, designers, marketers, and developer advocates. This variety shows just how many teams are involved and invested in documentation today.

We also conducted interviews with a number of technical writers, engineers, and documentation leaders from across the tech industry to get their insights into specific areas — you can read quotes from them throughout the report.

TAKEAWAYS:

- 54% believe their docs generate at least as many leads as their marketing sites

- 42% think AI will let us build docs that intelligently adapt to user needs

- 46% of large companies have decentralized or hybrid docs teams"

stateofdocs.com/2025/

#TechnicalWriting #TechnicalCommunication #Documentation #SoftwareDocumentation #SoftwareDevelopment #AI #Marketing

Dione MaddernTwistappel
2025-04-30

I swear the document I'm editing keeps getting longer.

Now that I have been writing tooling to programmatically work with our docs, I have become an evangelist for improving docs through code.

Reviewed a proposal for some docs maintenance tasks yesterday, and my immediate thoughts (and comments!) were about how we could write tooling to automate the tasks.

Maintenance is always the first thing to get skipped when feature work gets busy. Automating maintenance tasks means they happen even when teams don’t have time to do them.

#TechnicalWriting

Back on the topic of auditing code examples in our documentation, part 5 of my 8-part series dives deep into the data model we used to store metadata and the code examples.

I look at the types of queries this model enables, performance implications, and future iteration. Data modeling is one of my favorite exercises, and I'm happy with the outcome for this project!

#TechnicalWriting #DeveloperDocs

dacharycarey.com/2025/04/27/au

Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-04-26

“When I say that tech writers should own the prompt that generates documentation, I mean two things: that they should design and maintain the prompts, and that they should spearhead docs automation initiatives themselves, as I suggested in my tech writing predictions for 2025. It’s not just about using LLMs at work or tolerating their existence: writers must lead the way and own the conversations with AIs around docs.

What Aikidocs aims at showing is that you can work with an LLM as you would with a tech savvy intern: you provide a style guide, concrete guidance, and source materials to get acceptable output on the other side of the black box. All the content created in those carefully fenced pens will follow your content strategy more than if you let opinionated tools do it for you.

It’s not vibe coding: it’s LLM surfing.”

passo.uno/build-tech-writing-t

#TechnicalWriting #SoftwareDocumentation #AI #GenerativeAI #LLMs

Yvonne Perkinsperkinsy@aus.social
2025-04-23

I had a lovely meetup coffee to start the day with fellow technical writers. Thank you to Swapnil for organising it.

#write_the_docs #TechnicalWriting #WTD #Melbourne

2025-04-23

Prominent pic in an article on koala culling with the caption "A kangaroo climbs a tree." As a tech writer, I understand how this happens. Still makes me cringe.

#technicalWriting #technicalWriting #cringe

msn.com/en-us/news/world/why-a

Pic in an article on koala culling with the caption "A kangaroo climbs a tree." The animal in the pic is a koala.
2025-04-20

Ever wondered how beforeEach works in unit test frameworks? Check out our new lifecycle diagram!

qunitjs.com/lifecycle/

People generally guess right when it comes to ordering, so why a diagram?

We want to show that the order is guaranteed, and showcase what's possible when you depend on it.

Thanks to FND, Jan, and NullVoxPopuli for improving and promoting this work! H/T @FND @simulo @nullvoxpopuli

#qunit #WriteTheDocs #TechnicalWriting #SoftwareDocumentation #documentation #TDD

Imagine a test with global hooks, and a Parent and Child module that use hooks also. The execution order is:
1. Parent module runs the before hook.
2. Every test in the Parent module inherits context from the before hook, and repeats as follows: call global beforeEach, parent beforeEach, the actual test, parent afterEach, and lastly the global afterEach.
3. The Child module inherits context from the Parent before hook, and then runs its own before hook.
4. Every test in the Child module inherits context from this before hook, and repeats as follows: call global beforeEach, parent beforeEach, child beforeEach, the actual test, child afterEach, parent afterEach, and lastly the global afterEach.
Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-04-19

"Most guides to docs like code, even the ones for non-devs, assume you have some developer knowledge: maybe you're already using version control, or you've encountered build pipelines before, or you're working alongside developers.

This guide is for the people who read that paragraph and wished it came with a glossary. This is docs like code for people who don't know what git is and have never installed VS Code.

This post explains terminology and concepts, to help you get a mental model of what's going on. If you prefer to dive in and pick up concepts as you go, skip straight to the tips in How to learn, and come back to the conceptual info as needed."

deborahwrites.com/blog/docs-li

#TechnicalWriting #SoftwareDocumentation #SoftwareDevelopment #Programming #DocsAsCode #Git #Markdown #TechnicalCommunication #MkDocs #VSCode

Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-04-19

"When evaluating documentation’s role, consider these broader strategic questions:

- Strategic positioning: How does documentation support the company’s core strategic approach?

- Competitive advantage: Can documentation create or enhance the company’s unique market position? What type of documentation does the competition offer?

- Value proposition: How does documentation contribute to the product’s overall value for customers?

- Knowledge management: How does documentation support internal knowledge retention and transfer?

- Customer lifecycle: How can documentation improve customer acquisition, retention, and satisfaction?"

thegooddocsproject.dev/blog/ma

#TechnicalWriting #Documentation #SoftwareDocumentation #TechnicalCommunication

Miguel Afonso Caetanoremixtures@tldr.nettime.org
2025-04-19

"When evaluating documentation’s role, consider these broader strategic questions:

- Strategic positioning: How does documentation support the company’s core strategic approach?

- Competitive advantage: Can documentation create or enhance the company’s unique market position? What type of documentation does the competition offer?

- Value proposition: How does documentation contribute to the product’s overall value for customers?

- Knowledge management: How does documentation support internal knowledge retention and transfer?

- Customer lifecycle: How can documentation improve customer acquisition, retention, and satisfaction?"

thegooddocsproject.dev/blog/ma

#TechnicalWriting #Documentation #SoftwareDocumentation #TechnicalCommunication

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst