<?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: Dmitry Lezhnev</title>
    <description>The latest articles on DEV Community by Dmitry Lezhnev (@lezhnev74).</description>
    <link>https://dev.to/lezhnev74</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%2F169835%2Fe122f008-22d5-4299-9aee-318136c2cbbc.jpeg</url>
      <title>DEV Community: Dmitry Lezhnev</title>
      <link>https://dev.to/lezhnev74</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lezhnev74"/>
    <language>en</language>
    <item>
      <title>Playbook for Remote Development Teams</title>
      <dc:creator>Dmitry Lezhnev</dc:creator>
      <pubDate>Sat, 18 Feb 2023 18:01:18 +0000</pubDate>
      <link>https://dev.to/lezhnev74/playbook-for-remote-development-teams-3bob</link>
      <guid>https://dev.to/lezhnev74/playbook-for-remote-development-teams-3bob</guid>
      <description>&lt;p&gt;This is a short version of my blog post: &lt;a href="https://lessthan12ms.com/remote-teams-playbook.html"&gt;https://lessthan12ms.com/remote-teams-playbook.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This list contains my distilled ideas that came from working in quite a few teams and observing the industry, there are no two identical companies so I am aware of my limited exposure and probable naiveness. However, these insights came from my real experience and I can truly say that these things work and work well. I have worn many hats. Worked many years as a contractor/freelancer, then switched to small saas/mobile app startups (as CTO or a backend developer). I enjoy the most working at the backend with only two tools open: my IDE and my terminal (the rest is optional).&lt;/p&gt;

&lt;p&gt;The playbook contents:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Practices to deliver high-quality code in the long run.&lt;/li&gt;
&lt;li&gt;Cultural fit&lt;/li&gt;
&lt;li&gt;No Backlog&lt;/li&gt;
&lt;li&gt;Developers Autonomy&lt;/li&gt;
&lt;li&gt;Share Knowledge And Progress&lt;/li&gt;
&lt;li&gt;Clear Technical Standards And Expectations&lt;/li&gt;
&lt;li&gt;Supervised Onboarding&lt;/li&gt;
&lt;li&gt;Foreman&lt;/li&gt;
&lt;li&gt;Multi-phase code quality control&lt;/li&gt;
&lt;li&gt;CI/CD&lt;/li&gt;
&lt;li&gt;TDD&lt;/li&gt;
&lt;li&gt;SOLID principles&lt;/li&gt;
&lt;li&gt;Hexagonal(Clean) Architecture&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>remote</category>
      <category>team</category>
      <category>culture</category>
      <category>developer</category>
    </item>
  </channel>
</rss>
