home.social

#technicalwriter — Public Fediverse posts

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

fetched live
  1. I updated the Buttondown snippets documentation to explain a little bit more about what we were working with, as well as provide some keyboard navigation. It went live today! docs.buttondown.com/snippets #Newsletter #AmWriting #TechnicalWriter

  2. I updated the Buttondown snippets documentation to explain a little bit more about what we were working with, as well as provide some keyboard navigation. It went live today! docs.buttondown.com/snippets #Newsletter #AmWriting #TechnicalWriter

  3. I updated the Buttondown snippets documentation to explain a little bit more about what we were working with, as well as provide some keyboard navigation. It went live today! docs.buttondown.com/snippets #Newsletter #AmWriting #TechnicalWriter

  4. I updated the Buttondown snippets documentation to explain a little bit more about what we were working with, as well as provide some keyboard navigation. It went live today! docs.buttondown.com/snippets #Newsletter #AmWriting #TechnicalWriter

  5. I updated the Buttondown snippets documentation to explain a little bit more about what we were working with, as well as provide some keyboard navigation. It went live today! docs.buttondown.com/snippets #Newsletter #AmWriting #TechnicalWriter

  6. "Are we heading toward an AI utopia, an AI dystopia… or something in between?

    In this episode of Technical Writing Uncensored, I sit down with technical writer and blogger Fabrizio Ferri-Benedetti to talk about how AI and LLMs are changing technical writing — and what writers should actually be worried about.

    Fabri writes the excellent Passo Uno blog, where he explores technical writing, AI, and the future of documentation.
    Read his blog here: passo.uno

    We discuss whether AI will replace writers, how technical writers can stay relevant, and why writers might actually become more important in an AI-driven world.

    Fabri also explains why writers should think of AI as “a second language”, not something that replaces human expertise.

    We also discuss:
    Why AI is more like a tool (a hammer) than an autonomous intelligence
    Why good documentation is essential for AI systems
    Whether tech writers will become editors and prompt architects
    Why writers need a “mental gym” to keep their thinking sharp

    This conversation is a thoughtful look at the real impact of AI on technical writing, without the hype.

    #TechnicalWritingUncensored #TechnicalWriter #TechnicalWriting #Documentarian #Documentation #WordNerds #TechComm #ContentStrategy #WritingTips #CareerAdvice #UserExperience #DocsLikeCode #TechWritingUncensored #TechCommunity #aiforwriters #ai #llm #artificialintelligence "

    youtube.com/watch?v=ueUDtIgcpgA

  7. "Are we heading toward an AI utopia, an AI dystopia… or something in between?

    In this episode of Technical Writing Uncensored, I sit down with technical writer and blogger Fabrizio Ferri-Benedetti to talk about how AI and LLMs are changing technical writing — and what writers should actually be worried about.

    Fabri writes the excellent Passo Uno blog, where he explores technical writing, AI, and the future of documentation.
    Read his blog here: passo.uno

    We discuss whether AI will replace writers, how technical writers can stay relevant, and why writers might actually become more important in an AI-driven world.

    Fabri also explains why writers should think of AI as “a second language”, not something that replaces human expertise.

    We also discuss:
    Why AI is more like a tool (a hammer) than an autonomous intelligence
    Why good documentation is essential for AI systems
    Whether tech writers will become editors and prompt architects
    Why writers need a “mental gym” to keep their thinking sharp

    This conversation is a thoughtful look at the real impact of AI on technical writing, without the hype.

    #TechnicalWritingUncensored #TechnicalWriter #TechnicalWriting #Documentarian #Documentation #WordNerds #TechComm #ContentStrategy #WritingTips #CareerAdvice #UserExperience #DocsLikeCode #TechWritingUncensored #TechCommunity #aiforwriters #ai #llm #artificialintelligence "

    youtube.com/watch?v=ueUDtIgcpgA

  8. "Are we heading toward an AI utopia, an AI dystopia… or something in between?

    In this episode of Technical Writing Uncensored, I sit down with technical writer and blogger Fabrizio Ferri-Benedetti to talk about how AI and LLMs are changing technical writing — and what writers should actually be worried about.

    Fabri writes the excellent Passo Uno blog, where he explores technical writing, AI, and the future of documentation.
    Read his blog here: passo.uno

    We discuss whether AI will replace writers, how technical writers can stay relevant, and why writers might actually become more important in an AI-driven world.

    Fabri also explains why writers should think of AI as “a second language”, not something that replaces human expertise.

    We also discuss:
    Why AI is more like a tool (a hammer) than an autonomous intelligence
    Why good documentation is essential for AI systems
    Whether tech writers will become editors and prompt architects
    Why writers need a “mental gym” to keep their thinking sharp

    This conversation is a thoughtful look at the real impact of AI on technical writing, without the hype.

    #TechnicalWritingUncensored #TechnicalWriter #TechnicalWriting #Documentarian #Documentation #WordNerds #TechComm #ContentStrategy #WritingTips #CareerAdvice #UserExperience #DocsLikeCode #TechWritingUncensored #TechCommunity #aiforwriters #ai #llm #artificialintelligence "

    youtube.com/watch?v=ueUDtIgcpgA

  9. "Are we heading toward an AI utopia, an AI dystopia… or something in between?

    In this episode of Technical Writing Uncensored, I sit down with technical writer and blogger Fabrizio Ferri-Benedetti to talk about how AI and LLMs are changing technical writing — and what writers should actually be worried about.

    Fabri writes the excellent Passo Uno blog, where he explores technical writing, AI, and the future of documentation.
    Read his blog here: passo.uno

    We discuss whether AI will replace writers, how technical writers can stay relevant, and why writers might actually become more important in an AI-driven world.

    Fabri also explains why writers should think of AI as “a second language”, not something that replaces human expertise.

    We also discuss:
    Why AI is more like a tool (a hammer) than an autonomous intelligence
    Why good documentation is essential for AI systems
    Whether tech writers will become editors and prompt architects
    Why writers need a “mental gym” to keep their thinking sharp

    This conversation is a thoughtful look at the real impact of AI on technical writing, without the hype.

    #TechnicalWritingUncensored #TechnicalWriter #TechnicalWriting #Documentarian #Documentation #WordNerds #TechComm #ContentStrategy #WritingTips #CareerAdvice #UserExperience #DocsLikeCode #TechWritingUncensored #TechCommunity #aiforwriters #ai #llm #artificialintelligence "

    youtube.com/watch?v=ueUDtIgcpgA

  10. "Are we heading toward an AI utopia, an AI dystopia… or something in between?

    In this episode of Technical Writing Uncensored, I sit down with technical writer and blogger Fabrizio Ferri-Benedetti to talk about how AI and LLMs are changing technical writing — and what writers should actually be worried about.

    Fabri writes the excellent Passo Uno blog, where he explores technical writing, AI, and the future of documentation.
    Read his blog here: passo.uno

    We discuss whether AI will replace writers, how technical writers can stay relevant, and why writers might actually become more important in an AI-driven world.

    Fabri also explains why writers should think of AI as “a second language”, not something that replaces human expertise.

    We also discuss:
    Why AI is more like a tool (a hammer) than an autonomous intelligence
    Why good documentation is essential for AI systems
    Whether tech writers will become editors and prompt architects
    Why writers need a “mental gym” to keep their thinking sharp

    This conversation is a thoughtful look at the real impact of AI on technical writing, without the hype.

    #TechnicalWritingUncensored #TechnicalWriter #TechnicalWriting #Documentarian #Documentation #WordNerds #TechComm #ContentStrategy #WritingTips #CareerAdvice #UserExperience #DocsLikeCode #TechWritingUncensored #TechCommunity #aiforwriters #ai #llm #artificialintelligence "

    youtube.com/watch?v=ueUDtIgcpgA

  11. How to use Notebook Navigator (Obsidian Community plug-in)

    I wrote Aasimple, straightforward Users' Guide to Obsidian community plug-in Notebook Navigator.

    elizabethtai.com/2025/11/25/ho

    #Obsidian #Techwriting #TechnicalWriter

  12. How to use Notebook Navigator (Obsidian Community plug-in)

    I wrote Aasimple, straightforward Users' Guide to Obsidian community plug-in Notebook Navigator.

    elizabethtai.com/2025/11/25/ho

    #Obsidian #Techwriting #TechnicalWriter

  13. How to use Notebook Navigator (Obsidian Community plug-in)

    I wrote Aasimple, straightforward Users' Guide to Obsidian community plug-in Notebook Navigator.

    elizabethtai.com/2025/11/25/ho

  14. How to use Notebook Navigator (Obsidian Community plug-in)

    I wrote Aasimple, straightforward Users' Guide to Obsidian community plug-in Notebook Navigator.

    elizabethtai.com/2025/11/25/ho

    #Obsidian #Techwriting #TechnicalWriter

  15. How to use Notebook Navigator (Obsidian Community plug-in)

    I wrote Aasimple, straightforward Users' Guide to Obsidian community plug-in Notebook Navigator.

    elizabethtai.com/2025/11/25/ho

    #Obsidian #Techwriting #TechnicalWriter

  16. When will I learn? I'm playing around with #craiyon and it just can't wrap is tin brain around creating a picture of polymath #engineer #technicalwriter #RufusTurner in a logo. Here's a photo of Turner and the following are images of the logos. The only way to get a correct image was to use the qualifier #black or #blackman. Why is there an assumption in these modern times that all engineers are #white? #BlackMastodon #RadioHistory #wireless 1/3

  17. When will I learn? I'm playing around with #craiyon and it just can't wrap is tin brain around creating a picture of polymath #engineer #technicalwriter #RufusTurner in a logo. Here's a photo of Turner and the following are images of the logos. The only way to get a correct image was to use the qualifier #black or #blackman. Why is there an assumption in these modern times that all engineers are #white? #BlackMastodon #RadioHistory #wireless 1/3

  18. When will I learn? I'm playing around with #craiyon and it just can't wrap is tin brain around creating a picture of polymath #engineer #technicalwriter #RufusTurner in a logo. Here's a photo of Turner and the following are images of the logos. The only way to get a correct image was to use the qualifier #black or #blackman. Why is there an assumption in these modern times that all engineers are #white? #BlackMastodon #RadioHistory #wireless 1/3

  19. When will I learn? I'm playing around with #craiyon and it just can't wrap is tin brain around creating a picture of polymath #engineer #technicalwriter #RufusTurner in a logo. Here's a photo of Turner and the following are images of the logos. The only way to get a correct image was to use the qualifier #black or #blackman. Why is there an assumption in these modern times that all engineers are #white? #BlackMastodon #RadioHistory #wireless 1/3

  20. When will I learn? I'm playing around with #craiyon and it just can't wrap is tin brain around creating a picture of polymath #engineer #technicalwriter #RufusTurner in a logo. Here's a photo of Turner and the following are images of the logos. The only way to get a correct image was to use the qualifier #black or #blackman. Why is there an assumption in these modern times that all engineers are #white? #BlackMastodon #RadioHistory #wireless 1/3

  21. Are you looking for a new role in #OpenSource? Search jobs now on #OSJH and set up job alerts to find out when new positions are posted -- no registration necessary!
    opensourcejobhub.com?utm_sourc
    #career #software #engineer #sales #marketing #TechnicalWriter #security #SRE #developer

  22. Are you looking for a new role in ? Search jobs now on and set up job alerts to find out when new positions are posted -- no registration necessary!
    opensourcejobhub.com?utm_sourc

  23. Are you looking for a new role in #OpenSource? Search jobs now on #OSJH and set up job alerts to find out when new positions are posted -- no registration necessary!
    opensourcejobhub.com?utm_sourc
    #career #software #engineer #sales #marketing #TechnicalWriter #security #SRE #developer

  24. Are you looking for a new role in #OpenSource? Search jobs now on #OSJH and set up job alerts to find out when new positions are posted -- no registration necessary!
    opensourcejobhub.com?utm_sourc
    #career #software #engineer #sales #marketing #TechnicalWriter #security #SRE #developer

  25. Are you looking for a new role in #OpenSource? Search jobs now on #OSJH and set up job alerts to find out when new positions are posted -- no registration necessary!
    opensourcejobhub.com?utm_sourc
    #career #software #engineer #sales #marketing #TechnicalWriter #security #SRE #developer

  26. "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

  27. "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

  28. "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

  29. "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

  30. "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

  31. "Let me be blunt.

    If your startup offers APIs and you don’t have a portal, you’re lighting developer acquisition money on fire. 💵 🧯🚒

    Here’s what a good portal actually does:

    Shortens time-to-value: faster POCs, faster adoption.

    Reduces support tickets: devs can find what they need.

    Builds trust: your API feels stable, documented, and ready.

    Increases conversion: when docs show how easy it is to integrate, not just tell.

    Still sending PDF onboarding packets to partners?

    C’mon, boo. 🥲"

    quetzalliwrites.com/newsletter

    #DevPortals #DeveloperPortals #APIs #API #APIDocumentation #TechnicalWriter #TechnicalCommunication

  32. "Let me be blunt.

    If your startup offers APIs and you don’t have a portal, you’re lighting developer acquisition money on fire. 💵 🧯🚒

    Here’s what a good portal actually does:

    Shortens time-to-value: faster POCs, faster adoption.

    Reduces support tickets: devs can find what they need.

    Builds trust: your API feels stable, documented, and ready.

    Increases conversion: when docs show how easy it is to integrate, not just tell.

    Still sending PDF onboarding packets to partners?

    C’mon, boo. 🥲"

    quetzalliwrites.com/newsletter

    #DevPortals #DeveloperPortals #APIs #API #APIDocumentation #TechnicalWriter #TechnicalCommunication

  33. "Let me be blunt.

    If your startup offers APIs and you don’t have a portal, you’re lighting developer acquisition money on fire. 💵 🧯🚒

    Here’s what a good portal actually does:

    Shortens time-to-value: faster POCs, faster adoption.

    Reduces support tickets: devs can find what they need.

    Builds trust: your API feels stable, documented, and ready.

    Increases conversion: when docs show how easy it is to integrate, not just tell.

    Still sending PDF onboarding packets to partners?

    C’mon, boo. 🥲"

    quetzalliwrites.com/newsletter

    #DevPortals #DeveloperPortals #APIs #API #APIDocumentation #TechnicalWriter #TechnicalCommunication

  34. "Let me be blunt.

    If your startup offers APIs and you don’t have a portal, you’re lighting developer acquisition money on fire. 💵 🧯🚒

    Here’s what a good portal actually does:

    Shortens time-to-value: faster POCs, faster adoption.

    Reduces support tickets: devs can find what they need.

    Builds trust: your API feels stable, documented, and ready.

    Increases conversion: when docs show how easy it is to integrate, not just tell.

    Still sending PDF onboarding packets to partners?

    C’mon, boo. 🥲"

    quetzalliwrites.com/newsletter

    #DevPortals #DeveloperPortals #APIs #API #APIDocumentation #TechnicalWriter #TechnicalCommunication

  35. "Let me be blunt.

    If your startup offers APIs and you don’t have a portal, you’re lighting developer acquisition money on fire. 💵 🧯🚒

    Here’s what a good portal actually does:

    Shortens time-to-value: faster POCs, faster adoption.

    Reduces support tickets: devs can find what they need.

    Builds trust: your API feels stable, documented, and ready.

    Increases conversion: when docs show how easy it is to integrate, not just tell.

    Still sending PDF onboarding packets to partners?

    C’mon, boo. 🥲"

    quetzalliwrites.com/newsletter

    #DevPortals #DeveloperPortals #APIs #API #APIDocumentation #TechnicalWriter #TechnicalCommunication

  36. I’m looking for work again! Anyone hiring out there? I am a content writer, I have written jokes for podcasts, technical writer, copywriter. Help! #jobs #tech #technicalwriter #forhire

  37. I’m looking for work again! Anyone hiring out there? I am a content writer, I have written jokes for podcasts, technical writer, copywriter. Help! #jobs #tech #technicalwriter #forhire

  38. I’m looking for work again! Anyone hiring out there? I am a content writer, I have written jokes for podcasts, technical writer, copywriter. Help! #jobs #tech #technicalwriter #forhire

  39. I’m looking for work again! Anyone hiring out there? I am a content writer, I have written jokes for podcasts, technical writer, copywriter. Help! #jobs #tech #technicalwriter #forhire

  40. I’m looking for work again! Anyone hiring out there? I am a content writer, I have written jokes for podcasts, technical writer, copywriter. Help! #jobs #tech #technicalwriter #forhire

  41. Dear #developers (and #productmanagement that enables this) - if you're too lazy to remove a dead or unfinished feature that is *visible* to the user... and got QA to ignore/bless it....

    Don't. TAKE IT OUT. HIDE with a registry flag. DO ANYTHING don't just leave it fucking sitting there.

    - Sincerely, the #technicalwriter who has to put "Oh this button right here? Ignore that it doesn't do anything" in the help/manual/marketing material.

    It looks like shit and it makes us look like morons.

  42. Dear #developers (and #productmanagement that enables this) - if you're too lazy to remove a dead or unfinished feature that is *visible* to the user... and got QA to ignore/bless it....

    Don't. TAKE IT OUT. HIDE with a registry flag. DO ANYTHING don't just leave it fucking sitting there.

    - Sincerely, the #technicalwriter who has to put "Oh this button right here? Ignore that it doesn't do anything" in the help/manual/marketing material.

    It looks like shit and it makes us look like morons.

  43. Dear #developers (and #productmanagement that enables this) - if you're too lazy to remove a dead or unfinished feature that is *visible* to the user... and got QA to ignore/bless it....

    Don't. TAKE IT OUT. HIDE with a registry flag. DO ANYTHING don't just leave it fucking sitting there.

    - Sincerely, the #technicalwriter who has to put "Oh this button right here? Ignore that it doesn't do anything" in the help/manual/marketing material.

    It looks like shit and it makes us look like morons.

  44. Dear (and that enables this) - if you're too lazy to remove a dead or unfinished feature that is *visible* to the user... and got QA to ignore/bless it....

    Don't. TAKE IT OUT. HIDE with a registry flag. DO ANYTHING don't just leave it fucking sitting there.

    - Sincerely, the who has to put "Oh this button right here? Ignore that it doesn't do anything" in the help/manual/marketing material.

    It looks like shit and it makes us look like morons.

  45. Dear #developers (and #productmanagement that enables this) - if you're too lazy to remove a dead or unfinished feature that is *visible* to the user... and got QA to ignore/bless it....

    Don't. TAKE IT OUT. HIDE with a registry flag. DO ANYTHING don't just leave it fucking sitting there.

    - Sincerely, the #technicalwriter who has to put "Oh this button right here? Ignore that it doesn't do anything" in the help/manual/marketing material.

    It looks like shit and it makes us look like morons.