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


<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" version="2.0">
   <channel>
      <title>
	Comments for Work Life by Atlassian	</title>
      <atom:link href="https://www.atlassian.com/comments/feed" rel="self" type="application/rss+xml"/>
      <link>https://www.atlassian.com/blog</link>
      <description>Unleashing the potential of all teams with tips, tools, and practices</description>
      <lastBuildDate>Thu, 15 Jan 2026 06:36:19 +0000</lastBuildDate>
      <sy:updatePeriod>
	hourly	</sy:updatePeriod>
      <sy:updateFrequency>
	1	</sy:updateFrequency>
      <item>
         <title>
		Comment on Generate Bitbucket Cloud pull request descriptions with Atlassian Intelligence by Создать личный аккаунт		</title>
         <link>https://www.atlassian.com/blog/bitbucket/generate-pull-request-descriptions-with-atlassian-intelligence#comment-25416</link>
         <dc:creator>Создать личный аккаунт</dc:creator>
         <pubDate>Thu, 15 Jan 2026 06:36:19 +0000</pubDate>
         <guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/generate-pull-request-descriptions-with-atlassian-intelligence#comment-25416</guid>
         <description>Your point of view caught my eye and was very interesting. Thanks. I have a question for you.</description>
         <content:encoded>&lt;p&gt;Your point of view caught my eye and was very interesting. Thanks. I have a question for you.&lt;/p&gt;
</content:encoded>
      </item>
      <item>
         <title>
		Comment on More power and more control: the power-ups menu is moving by binance odprt racun		</title>
         <link>https://www.atlassian.com/blog/add-ons/power-ups-menu#comment-25415</link>
         <dc:creator>binance odprt racun</dc:creator>
         <pubDate>Thu, 15 Jan 2026 05:32:24 +0000</pubDate>
         <guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/power-ups-menu#comment-25415</guid>
         <description>Your point of view caught my eye and was very interesting. Thanks. I have a question for you.</description>
         <content:encoded>&lt;p&gt;Your point of view caught my eye and was very interesting. Thanks. I have a question for you.&lt;/p&gt;
</content:encoded>
      </item>
      <item>
         <title>
		Comment on 9 Software Documentation Best Practices + Real Examples by How to Build Internal Documentation That Growing Tech Teams Actually Use - Space Coast Daily		</title>
         <link>https://www.atlassian.com/blog/loom/software-documentation-best-practices#comment-25414</link>
         <dc:creator>How to Build Internal Documentation That Growing Tech Teams Actually Use - Space Coast Daily</dc:creator>
         <pubDate>Thu, 15 Jan 2026 04:15:00 +0000</pubDate>
         <guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/software-documentation-best-practices#comment-25414</guid>
         <description>[&amp;#8230;] of contents, and an intuitive structure reduce frustration and make information easy to navigate [14]. Documentation organized by process helps preempt potential questions, addressing them before they [&amp;#8230;]</description>
         <content:encoded>&lt;p&gt;[&amp;#8230;] of contents, and an intuitive structure reduce frustration and make information easy to navigate [14]. Documentation organized by process helps preempt potential questions, addressing them before they [&amp;#8230;]&lt;/p&gt;
</content:encoded>
      </item>
      <item>
         <title>
		Comment on Rethinking your product team structure for better focus and scale by Thng dang k'y binance		</title>
         <link>https://www.atlassian.com/blog/developer/rethinking-your-product-team-structure-for-better-focus-and-scale#comment-25413</link>
         <dc:creator>Thng dang k'y binance</dc:creator>
         <pubDate>Thu, 15 Jan 2026 02:37:12 +0000</pubDate>
         <guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/rethinking-your-product-team-structure-for-better-focus-and-scale#comment-25413</guid>
         <description>Your article helped me a lot, is there any more related content? Thanks! https://accounts.binance.com/sv/register-person?ref=GQ1JXNRE</description>
         <content:encoded>&lt;p&gt;Your article helped me a lot, is there any more related content? Thanks! &lt;a href="https://accounts.binance.com/sv/register-person?ref=GQ1JXNRE" rel="nofollow ugc"&gt;https://accounts.binance.com/sv/register-person?ref=GQ1JXNRE&lt;/a&gt;&lt;/p&gt;
</content:encoded>
      </item>
      <item>
         <title>
		Comment on How to excel at asynchronous communication with your distributed team by The Coffee Kitchen Myth: Why Proximity Is Overrated and Digital Colleagueship Actually Works - MI Hub		</title>
         <link>https://www.atlassian.com/blog/communication/asynchronous-communication-for-distributed-teams#comment-25412</link>
         <dc:creator>The Coffee Kitchen Myth: Why Proximity Is Overrated and Digital Colleagueship Actually Works - MI Hub</dc:creator>
         <pubDate>Wed, 14 Jan 2026 21:50:28 +0000</pubDate>
         <guid isPermaLink="false">https://www.atlassian.com/blog/?p=54373#comment-25412</guid>
         <description>[&amp;#8230;] Hallway proximity is synchronous by default: you catch someone, interrupt them, and hope the moment is good. Async collaboration flips the burden: it allows people to respond with context, time, and thought—often producing better decisions and less resentment. Atlassian&amp;#8217;s guidance on asynchronous communication emphasizes intentional habits and shared norms so distributed teams can align without constant real-time interruption, outlined in Atlassian&amp;#8217;s async communication playbook. [&amp;#8230;]</description>
         <content:encoded>&lt;p&gt;[&amp;#8230;] Hallway proximity is synchronous by default: you catch someone, interrupt them, and hope the moment is good. Async collaboration flips the burden: it allows people to respond with context, time, and thought—often producing better decisions and less resentment. Atlassian&amp;#8217;s guidance on asynchronous communication emphasizes intentional habits and shared norms so distributed teams can align without constant real-time interruption, outlined in Atlassian&amp;#8217;s async communication playbook. [&amp;#8230;]&lt;/p&gt;
</content:encoded>
      </item>
   </channel>
</rss>