home.social

#writethedocs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #writethedocs, aggregated by home.social.

  1. Folks, still a few weeks left to propose a talk to Write the Docs Berlin, Sep 6-8, 2026. writethedocs.org/conf/berlin/2

    Would love to see all your ideas about documentation and adjacent topics while I'm still buzzing from the Portland conference. #writethedocs

  2. Folks, still a few weeks left to propose a talk to Write the Docs Berlin, Sep 6-8, 2026. writethedocs.org/conf/berlin/2

    Would love to see all your ideas about documentation and adjacent topics while I'm still buzzing from the Portland conference. #writethedocs

  3. Folks, still a few weeks left to propose a talk to Write the Docs Berlin, Sep 6-8, 2026. writethedocs.org/conf/berlin/2

    Would love to see all your ideas about documentation and adjacent topics while I'm still buzzing from the Portland conference. #writethedocs

  4. Folks, still a few weeks left to propose a talk to Write the Docs Berlin, Sep 6-8, 2026. writethedocs.org/conf/berlin/2

    Would love to see all your ideas about documentation and adjacent topics while I'm still buzzing from the Portland conference. #writethedocs

  5. Folks, still a few weeks left to propose a talk to Write the Docs Berlin, Sep 6-8, 2026. writethedocs.org/conf/berlin/2

    Would love to see all your ideas about documentation and adjacent topics while I'm still buzzing from the Portland conference. #writethedocs

  6. #WriteTheDocs just released a bunch of new videos from their most recent conference and unfortunately some of them shill AI, but one video caught my attention and is definitely worth watching: The Most Human Documentation.

    It talks about the things to avoid in order to not be mistaken by machine generation, and what it means for your #TechnicalWriting and #Documentation to feel human. The talk comments on this from a cultural perspective and it matches what I've been thinking about recently.

    With the rise of LLMs and their gross effect on online text now there's humans that work on humanizing machine content, be it with deterministic tools or with humans. In the end humans prefer content that feels human, and human content continues to provide more value.

  7. #WriteTheDocs just released a bunch of new videos from their most recent conference and unfortunately some of them shill AI, but one video caught my attention and is definitely worth watching: The Most Human Documentation.

    It talks about the things to avoid in order to not be mistaken by machine generation, and what it means for your #TechnicalWriting and #Documentation to feel human. The talk comments on this from a cultural perspective and it matches what I've been thinking about recently.

    With the rise of LLMs and their gross effect on online text now there's humans that work on humanizing machine content, be it with deterministic tools or with humans. In the end humans prefer content that feels human, and human content continues to provide more value.

  8. #WriteTheDocs just released a bunch of new videos from their most recent conference and unfortunately some of them shill AI, but one video caught my attention and is definitely worth watching: The Most Human Documentation.

    It talks about the things to avoid in order to not be mistaken by machine generation, and what it means for your #TechnicalWriting and #Documentation to feel human. The talk comments on this from a cultural perspective and it matches what I've been thinking about recently.

    With the rise of LLMs and their gross effect on online text now there's humans that work on humanizing machine content, be it with deterministic tools or with humans. In the end humans prefer content that feels human, and human content continues to provide more value.

  9. #WriteTheDocs just released a bunch of new videos from their most recent conference and unfortunately some of them shill AI, but one video caught my attention and is definitely worth watching: The Most Human Documentation.

    It talks about the things to avoid in order to not be mistaken by machine generation, and what it means for your #TechnicalWriting and #Documentation to feel human. The talk comments on this from a cultural perspective and it matches what I've been thinking about recently.

    With the rise of LLMs and their gross effect on online text now there's humans that work on humanizing machine content, be it with deterministic tools or with humans. In the end humans prefer content that feels human, and human content continues to provide more value.

  10. Avoiding the docs slide into staleness takes some proactive effort. But a lot of that can be automated these days.

    I talk about some suggestions in a blog post here: djw.fyi/portfolio/preventing-d

    #WriteTheDocs #docs #TechnicalWriting #DocOps #LLMOps

  11. Avoiding the docs slide into staleness takes some proactive effort. But a lot of that can be automated these days.

    I talk about some suggestions in a blog post here: djw.fyi/portfolio/preventing-d

    #WriteTheDocs #docs #TechnicalWriting #DocOps #LLMOps

  12. Avoiding the docs slide into staleness takes some proactive effort. But a lot of that can be automated these days.

    I talk about some suggestions in a blog post here: djw.fyi/portfolio/preventing-d

    #WriteTheDocs #docs #TechnicalWriting #DocOps #LLMOps

  13. Avoiding the docs slide into staleness takes some proactive effort. But a lot of that can be automated these days.

    I talk about some suggestions in a blog post here: djw.fyi/portfolio/preventing-d

    #WriteTheDocs #docs #TechnicalWriting #DocOps #LLMOps

  14. Avoiding the docs slide into staleness takes some proactive effort. But a lot of that can be automated these days.

    I talk about some suggestions in a blog post here: djw.fyi/portfolio/preventing-d

    #WriteTheDocs #docs #TechnicalWriting #DocOps #LLMOps

  15. As it turns out, I have Thoughts and Opinions about docs. Who knew?

    Amazing what years and years of doing something and building a skill (no, not the Clause kind) does

    #WriteTheDocs #documentation #docs

  16. Our Write The Docs booth was a hit yesterday at the DDD Melbourne conference. Even during sessions we had lots of people coming to our booth.

    Our BrickDocs Challenge was great. Even after a 3 minute quick exercise we had a few young developers have a light bulb moment when they realised the consequences of bad documentation for tired support staff managing an incident. Hopefully they will take additional care with writing their documentation after this.

    We were talking non-stop all day while we were manning the booth. There was a lot of noise in our area as people were having conversations at other booths too. Even with having shifts on/off I have come away with quite a strained voice.

    I really need to do vocal warm-up exercises before conducting workshops and manning conference booths like this. Feel free to share any tips you may have.

    #DDDMelb #WriteTheDocs #TechWriting #TechnicalWriting

  17. #dddmelb Had a great start to DDD helping to man the Write The Docs booth. Lots of people came to chat and try the Brick Docs Challenge. Loads of fun.

    If you are at DDD drop by our booth and say hi.
    #WriteTheDocs #TechWriting

  18. If you are going to the DDD conference in Melbourne tomorrow, head over to the Write The Docs booth and say hi. See if you can solve our 3 minute BrickDocs Challenge or join in some Docs Bingo.
    #dddmelb #WriteTheDocs #TechWriting #TechnicalWriting #KnowledgeManagement

    DDD Melbourne | 21st February 2026
    dddmelbourne.com/

  19. I have had a hard week but done very good work. I have found myself a delightful cafe in a working class suburb that has BOOKS!

    I am reading Don Watson's Dictionary of Weasel Words over breakfast. It was sitting in a small bookcase amongst the usual fantasy books and books about sporting greats.

    I am loving the intro. After talking about the manipulation of language by totalitarian states and how the subdued masses adopt that language, Watson says:

    "The same mimicry can be expected wherever the official language is a kind of code that we must at least appear to understand, or be excluded. It happens in democracies, and in business and government departments."

    How often have you found when starting a new job that you ate desperately trying to use the acronyms, the phrases and names that are bandied around the office to show that you fit in, that you are a 'valuable team member'?

    #jargon #acronyms #Management #TechnicalWriting #TechWriting #WriteTheDocs

  20. Writing is often the smallest part of a tech writer's day. Consider our work as a kind of super QA team and alpha tester that goes beyond making sure the software works as the ticket describes, for example.

    Read more:

    djw.fyi/posts/tech-writer-as-q

    #techWriting #documentation #writeTheDocs #docs

  21. The pushback against AI slop is making employers recognise the importance of skilled writing by humans so they are now hiring "storytellers":
    "It’s so much more than a copywriter,” says one hirer: wsj.com/articles/companies-are

    Hopefully this will see a move beyond hiring copywriters to keyword stuff for SEO and AI, a move beyond judging skill by simplistic metrics such as number of boosts, likes etc. I hope that organisations will want professional writers who can identify target audiences and deliver meaningful material that will be valued by those audiences. This is true success, but may mean that the post or article might not get many clicks.

    I hope that over time "storyteller" will not simply become a synonym for "copywriter".

    Technical writers already provide this kind of skill when writing about technology, or health, or science, or digital humanities

    #WriteTheDocs #TechWriting #TechnicalWriting #TechnicalWriters #DigitalHumanities

  22. Just a couple of tickets left now for my Writing design systems documentation session at 10am-1pm next Thursday, 29 May.

    If you're available and want to learn how to create docs people can find, understand and use, I'd love to have you.

    Tell your friends!

    bit.ly/4j2rW2D

    #UXWriting #WriteTheDocs #DesignSystems

  23. 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

  24. A pic I took on the streets of #Portland
    # 363 days ago, area within walking distance of #Revolution Hall.

    I've remained publicly silent on my #WriteTheDocs conference attendance last year because it was .... a shitty conference.

    And today I'll tell you why it was a shitty conference.

    There was a self-proclaimed "extrovert" who got up on stage and vomited bullshit about how she was representing #Nginx.

    I did not plan to give a talk, but when I woke up the last day of the conference, I really had this pressing intuition that I should speak up for the talent that was maybe intimidated ... that NO, you don't need a fucking Macbook to be a technical writer... not all technical writing is about computer-related things.

    But then did I find out ... what that Nginx "extrovert" was really there to do was be the shithead #censoring the indigenous voice that wanted to get on stage and tell everybody that not all #TechnicalWriting has to be about #technology.

    But that snooty white supremacist bitch rejected this talk.

  25. I'm drafting a diagram to explain how before/after hooks work in unit tests.

    They tend to work the same way across test frameworks, so it's not unique to QUnit. But, new devs will learn this for the first time, so I think it's worth explaining.

    Page:
    qunitjs.com/api/QUnit/module/#

    Issue tracker:
    github.com/qunitjs/qunit/issue

    What do you think?

  26. Only a couple of weeks left to get your documentation related talk proposal in for the next Write the Docs conference, held May 4-6 Portland.

    ➡️ writethedocs.org/conf/portland

    #writethedocs #techcomm #documentation #cfp

  27. We have been busy this year developing the idea of a Brick Docs Workshop designed to help IT engineers develop technical writing skills. This fun workshop uses Lego to identify writing and formatting techniques that help make instructions clearer.

    We are running this workshop at the national technical writing conference in Melbourne next week. DM me if you want to attend - I can see if I can wangle some tickets.
    #TechnicalWriters #WriteTheDocs #Melbourne

    writethedocs.org/conf/australi

  28. Fantastic talk on crossover from DevOps and documentation by @lornajane at #writethedocs

    I’m still out here trying to make #DocOps a thing

  29. @remoquete THIS ☝️.

    I am fortunate that my manager recognises this critical juncture in technical writing and has given me substantial time to reimagine my job.

    I spoke about the benefits of working in the space between professional silos in my Linux Conference talk a few years ago: When STEM Becomes STEAM We All Benefit m.youtube.com/watch?v=oEX-F5Sx

    #TechnicalWriters #WriteTheDocs #documentation

  30. This is your reminder that we're just over two weeks out from the talk proposal deadline for Write the Docs Atlantic, an online conference about documentation.

    All the details are here writethedocs.org/conf/atlantic

    #techcomm #writethedocs #documentation #cfp #conference

    Retweets appreciated.

  31. The goal of this short and sweet style guide is to be "just enough" guidance for technical documentation contributors who aren't regular writers. Thank you Lorna Jane! github.com/lornajane/developer #opensource #techwriting #writethedocs #techcomm

  32. 🏹 I'll gift my #WriteTheDocs conference ticket to an indigenous woman who is aspiring to become a paid technical writer in her field of choice. .... "If I get that ONE job I'd really like." 🏹

    🏹 I'll promise to not turn my attendance at the #TechnicalWriter conference into a recruitment for uncompensated "volunteer" writers as long as I don't have to do a fundraiser for anything. I'll be the advocate for YOU. .... "If I get that OTHER job I really want."

    I had a peek of what retired life might be like... and I don't want it yet. My brain, heart, health all suffer when I'm isolated from statisticians and their interesting data streams.

    Was at a postal service mailing place the other day, and they measure in "ounces" and it just baffled me. I thought my "forever" stamps would be fine and dandy for the letters. Nope. I'm like... wtf is an ounce? I thought that was for liquids... Didn't I write some "TO METRIC SYSTEM" Conversion CODE for this? (And I did, will share it soon)

    I had to tell the lady that I didn't get it in the only way I knew how: "I studied science. I don't understand modern American measuring systems."

    In other interesting news THOUSANDS of people marched yesterday in Minnesota for #MMIP #MMIW #MMIWG. My Internet was down so I missed the live stream (was so sad)

    NDN Collective has some vids on the Public Interent of Paid Reporters (YouTube).

    I have not looked who else is reporting, but I sure hope they are getting paid well.

  33. I’ve seen an uptick in comments about needing to reduce the length of design system docs and thought it was a good time to reshare this post I co-wrote with @Cjforms on why the length of content is not a problem. The real issue is irrelevant information.

    #DesignSystems #UXDesign #UXWriting #WriteTheDocs

    amyhupe.co.uk/articles/dont-be

  34. There's this awesome talk by Ed Cormany given to #WriteTheDocs this year that I absolutely would recommend to anyone remotely interested in #Linguistics and #TechnicalWriting. It is very easy to understand the presented concepts.

    It's called "The Descriptivist Manifesto" (Youtube link / Invidious link).

    He talks about how we should approach rules and patterns in our writing from a #descriptivism point of view, demonstrating how this data-driven approach can be useful. Even the Q&A at the end is just as worth watching.

    Probably the biggest takeaway being that we should write about tech the way we talk about tech.

  35. If you're a #documentarian or #techwriter or otherwise interested in #documentation , check out #WriteTheDocs ! The Portland 2023 conference has an Opportunity grant for those who would otherwise have difficulty attending: writethedocs.org/conf/portland
    #noxp

  36. I'm obsessed with good #documentation and the Routinator user manual on #ReadTheDocs is my pride and joy.

    We worked very hard to seamlessly integrate the manual page into it as well, allowing us to automatically link command line options, but we also wanted it to be the canonical source for building the the manpage with rst2man. This saves us from keeping content in sync and messing with troff(1).

    github.com/NLnetLabs/routinato

    #WriteTheDocs #TechnicalWriting #TechnicalDocumentation #OpenSource

  37. In an effort to help us all find each other, I've been building a list of #techWriters and others connected to #WriteTheDocs. So my #followFriday submission this week (and probably for a few weeks) are all tech writers or adjacent:

    - @ericholscher (founded Write the Docs and Read the Docs)
    - @plaindocs
    - @jaredmorgs (also follow for #pinball content)
    - @straygoat
    - @rekiwi
    - @ellispratt
    - @alanpringle
    - @chrischinchilla
    - @josh
    - @swapnilogale (WTD #Australia!)
    - @ddbeck

    More next week!