<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Txai</title>
    <description>The latest articles on DEV Community by Txai (@txai).</description>
    <link>https://dev.to/txai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F70650%2F8415929c-99bc-413c-a860-6b4a58d4ed22.jpg</url>
      <title>DEV Community: Txai</title>
      <link>https://dev.to/txai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/txai"/>
    <language>en</language>
    <item>
      <title>Sharing pitfalls</title>
      <dc:creator>Txai</dc:creator>
      <pubDate>Wed, 05 Aug 2020 18:36:23 +0000</pubDate>
      <link>https://dev.to/txai/sharing-pitfalls-4boe</link>
      <guid>https://dev.to/txai/sharing-pitfalls-4boe</guid>
      <description>&lt;p&gt;Do you have some standard way to document your own failures, so others won't do the same thing when they encounter something similar? Like documenting when you waste a considerable time building something in a architecture that ended up being rebuild from the ground, or doing some fix that resulted in another bug being created, this kind of things.&lt;/p&gt;

</description>
      <category>discuss</category>
    </item>
  </channel>
</rss>
