<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" >

  <channel>
    <title><![CDATA[Статьи]]></title>
    <link>https://habr.com/ru/users/techwriter007/publications/articles/</link>
    <description><![CDATA[Хабр: статьи пользователя techwriter007]]></description>
    <language>ru</language>
    <managingEditor>editor@habr.com</managingEditor>
    <generator>habr.com</generator>
    <pubDate>Sun, 26 Apr 2026 22:10:30 GMT</pubDate>
    
    
      <image>
        <link>https://habr.com/ru/</link>
        <url>https://habrastorage.org/webt/ym/el/wk/ymelwk3zy1gawz4nkejl_-ammtc.png</url>
        <title>Хабр</title>
      </image>
    

    
      
        
    
    <item>
      <title><![CDATA[Собираем DOCX из ADOC]]></title>
      <guid isPermaLink="true">https://habr.com/ru/articles/801517/</guid>
      <link>https://habr.com/ru/articles/801517/?utm_campaign=801517&amp;utm_source=habrahabr&amp;utm_medium=rss</link>
      <description><![CDATA[<img src="https://habrastorage.org/getpro/habr/upload_files/c06/27c/53c/c0627c53c5df39fed3c6bdde7dd78346.png" /><p>Статья про то, как можно собрать docx-файл из git(adoc)-дерева.</p><p>По мнению автора, статья может быть интересна тем, кто хочет уйти от стандартных методов хранения документации. Ведь техническая документация всегда лежит на стыке кода, практик devops_а и нас, простых читателей.</p><p></p> <a href="https://habr.com/ru/articles/801517/?utm_campaign=801517&amp;utm_source=habrahabr&amp;utm_medium=rss#habracut">Читать далее</a>]]></description>
      
      <pubDate>Tue, 19 Mar 2024 19:36:11 GMT</pubDate>
      <dc:creator><![CDATA[techWriter007]]></dc:creator>
      <category><![CDATA[Подготовка технической документации]]></category>
      <category><![CDATA[docs-as-code]]></category><category><![CDATA[техническая документация]]></category><category><![CDATA[asciidoc]]></category>
    </item>
  

  

  

	
  

  

  

    
    <item>
      <title><![CDATA[Синдром хронического помешательства среди технических писателей]]></title>
      <guid isPermaLink="true">https://habr.com/ru/articles/750520/</guid>
      <link>https://habr.com/ru/articles/750520/?utm_campaign=750520&amp;utm_source=habrahabr&amp;utm_medium=rss</link>
      <description><![CDATA[<img src="https://habrastorage.org/getpro/habr/upload_files/410/f03/320/410f033204e2d2fdc5d43d9ff19aa3b0.jpg" /><p>Одной из малоприятных, но, увы, распространённых болезней, сопровождающих человека, который работает техническим писателем, является синдром хронического помешательства. Признаки заболевания обычно проявляются на третий год после начала работы техническим писателем и могут привести к преждевременному уходу с ума.</p><p></p> <a href="https://habr.com/ru/articles/750520/?utm_campaign=750520&amp;utm_source=habrahabr&amp;utm_medium=rss#habracut">Читать далее</a>]]></description>
      
      <pubDate>Wed, 26 Jul 2023 10:48:29 GMT</pubDate>
      <dc:creator><![CDATA[techWriter007]]></dc:creator>
      <category><![CDATA[Чулан]]></category><category><![CDATA[Читальный зал]]></category>
      <category><![CDATA[humor]]></category><category><![CDATA[documentation]]></category><category><![CDATA[technical writer]]></category>
    </item>
  

  

  

	
  

  

  

    
    <item>
      <title><![CDATA[The Role of the Technical Writer in the AI Revolution: Bridging the Gap between Technology and Communication]]></title>
      <guid isPermaLink="true">https://habr.com/en/articles/744930/</guid>
      <link>https://habr.com/en/articles/744930/?utm_campaign=744930&amp;utm_source=habrahabr&amp;utm_medium=rss</link>
      <description><![CDATA[<img src="https://habrastorage.org/getpro/habr/upload_files/42b/864/121/42b864121cabdd21b8775b14ba07e6b2.png" /><p>AI technologies offer unprecedented opportunities for innovation, efficiency, and growth in such industries as advanced machine learning algorithms or intelligent automation systems. However, to harness the power of AI, effective communication becomes paramount.</p><p>The growing impact of AI in modern business is undeniable. Organizations leverage AI to automate processes, gain insights from vast amounts of data, personalize customer experiences, and make informed decisions. Yet, the complex nature of AI technology often creates a significant gap between AI capabilities and the understanding of its users.</p><p>Here the role of a technical writer becomes crucial. Technical writers act as a bridge between AI technology and its users, ensuring that complex concepts have a clear, concise, and user-friendly manner of speaking. They are the main participants in making AI accessible to a broader audience, facilitating adoption, and maximizing its potential.</p><p>Effective communication is essential to reduce the gap between AI technology and its users. While AI systems may be sophisticated and comprehensive, their impact can be weak without proper understanding and utilization. Technical writers contribute to the success of AI implementations by translating complex AI concepts into easily digestible documentation, user manuals, tutorials, and other communication channels.</p><p>Furthermore, technical writers understand the importance of tailoring information for different audiences. They communicate with non-technical stakeholders, including executives, decision-makers, and end-users, who may lack extensive technical expertise. Using the AI capabilities, benefits, and potential limitations, technical writers empower these stakeholders to make informed decisions and embrace AI solutions.</p><p></p> <a href="https://habr.com/ru/articles/744930/?utm_campaign=744930&amp;utm_source=habrahabr&amp;utm_medium=rss#habracut">Read more</a>]]></description>
      
      <pubDate>Thu, 29 Jun 2023 19:37:22 GMT</pubDate>
      <dc:creator><![CDATA[techWriter007]]></dc:creator>
      <category><![CDATA[Читальный зал]]></category><category><![CDATA[Подготовка технической документации]]></category>
      <category><![CDATA[ai]]></category><category><![CDATA[technical writer]]></category><category><![CDATA[technical writing]]></category><category><![CDATA[documentation]]></category>
    </item>
  

  

  

	
  

  

  

      

      

      

    
  </channel>
</rss>
