<?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: Antoine Boulanger</title>
    <description>The latest articles on DEV Community by Antoine Boulanger (@antoineokay).</description>
    <link>https://dev.to/antoineokay</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%2F838997%2F2afe70c4-e1e6-46fb-98c8-b6f86d50b54a.jpeg</url>
      <title>DEV Community: Antoine Boulanger</title>
      <link>https://dev.to/antoineokay</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/antoineokay"/>
    <language>en</language>
    <item>
      <title>Sharing our open-source Engineering Effectiveness Handbook</title>
      <dc:creator>Antoine Boulanger</dc:creator>
      <pubDate>Tue, 29 Mar 2022 22:59:38 +0000</pubDate>
      <link>https://dev.to/antoineokay/sharing-our-open-source-engineering-effectiveness-handbook-c1</link>
      <guid>https://dev.to/antoineokay/sharing-our-open-source-engineering-effectiveness-handbook-c1</guid>
      <description>&lt;p&gt;Hi 👋 !&lt;/p&gt;

&lt;p&gt;tldr: we wrote a &lt;a href="https://www.okayhq.com/handbook"&gt;handbook&lt;/a&gt; on how to make engineering teams more effective&lt;/p&gt;

&lt;p&gt;We're former engineering leaders at Box, Google and Checkr and co-founders of a startup in the engineering effectiveness / productivity domain.&lt;/p&gt;

&lt;p&gt;Engineering effectiveness is about building metrics to detect common blockers like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;having too many meetings&lt;/li&gt;
&lt;li&gt;interruptions to your flow (pages, incidents, Slack)&lt;/li&gt;
&lt;li&gt;very long code reviews &lt;/li&gt;
&lt;li&gt;slow tooling / slow feedback loops&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After talking to and working with hundreds of engineers, we realized that while many team leaders want to build efficient teams, it's hard to know where to start.&lt;/p&gt;

&lt;p&gt;It's also important to avoid building any sort of surveillance tool in the process - metrics should focus on the developer experience.  &lt;/p&gt;

&lt;p&gt;We wrote an open-source handbook to answer all those questions, with a focus on &lt;strong&gt;practical, actionable advice&lt;/strong&gt; on how to build highly effective engineering teams. &lt;/p&gt;

&lt;p&gt;This first version covers topics such as how to manage your team's time, how to remove blockers in the software development life cycle, and how to get ahead of burn-out signals like on-call pages.&lt;/p&gt;

&lt;p&gt;We are welcoming contributions and feedback!&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.okayhq.com/handbook"&gt;Go to the hosted version of the handbook&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/OkayHQ/ee-handbook"&gt;Browse the Github repo&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>productivity</category>
      <category>management</category>
      <category>devops</category>
      <category>datascience</category>
    </item>
  </channel>
</rss>
