<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Leadership on Leonard Austin</title>
    <link>https://c05b76f5.leonardaustin.pages.dev/tags/leadership/</link>
    <description>Recent content in Leadership on Leonard Austin</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Sat, 10 Mar 2018 10:25:40 +0100</lastBuildDate>
    <atom:link href="https://c05b76f5.leonardaustin.pages.dev/tags/leadership/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Etiquette for Tech Teams</title>
      <link>https://c05b76f5.leonardaustin.pages.dev/posts/etiquette-for-tech-teams/</link>
      <pubDate>Sat, 10 Mar 2018 10:25:40 +0100</pubDate>
      <guid>https://c05b76f5.leonardaustin.pages.dev/posts/etiquette-for-tech-teams/</guid>
      <description>&lt;h2 id=&#34;for-a-happy-workplace&#34;&gt;For a Happy Workplace&lt;/h2&gt;&#xA;&lt;p&gt;This article attempts to offer some of the rules for a productive, cohesive and enjoyable working environment for tech teams. It is a semi-working article that I will add to over time.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://c05b76f5.leonardaustin.pages.dev/images/meetings.webp&#34; alt=&#34;meetings&#34;&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;meetings&#34;&gt;Meetings&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Always include an Agenda and Objective to meeting invites. It helps invitees decide whether the meeting is relevant to them.&lt;/li&gt;&#xA;&lt;li&gt;Long blocks of uninterrupted time is when the magic happens, for most engineers. Be mindful of this when scheduling meetings. The “best” time will differ depending on who you are inviting to the meeting.&lt;/li&gt;&#xA;&lt;li&gt;Default meeting duration is 30 minutes. Meetings longer than 1 hour tend to become unproductive: avoid them.&lt;/li&gt;&#xA;&lt;li&gt;Keep in mind everyone in the meeting, avoid tangents that are not applicable to the majority of the room. Stick to the agenda! Some conversations should just go into a ticket or google doc.&lt;/li&gt;&#xA;&lt;li&gt;At any point, excuse yourself from a meeting if it is not relevant to you.&lt;/li&gt;&#xA;&lt;li&gt;Announcing the meeting in #meetings slack channel. Don’t invite the whole company to every meeting, but allow people to invite themselves to things that are of interest to them.&lt;/li&gt;&#xA;&lt;li&gt;If you need a room make sure you book a room, so you’re not taking it from anybody else.&lt;/li&gt;&#xA;&lt;li&gt;Feel free to use your laptops in meetings unless the host specifically states otherwise.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://c05b76f5.leonardaustin.pages.dev/images/headphones.webp&#34; alt=&#34;headphones&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Engineering Team Core Values</title>
      <link>https://c05b76f5.leonardaustin.pages.dev/posts/engineering-team-core-values/</link>
      <pubDate>Mon, 15 Jan 2018 10:17:14 +0100</pubDate>
      <guid>https://c05b76f5.leonardaustin.pages.dev/posts/engineering-team-core-values/</guid>
      <description>&lt;h3 id=&#34;simple-code-is-elegant&#34;&gt;Simple Code is Elegant&lt;/h3&gt;&#xA;&lt;p&gt;Tidy, readable, simple code is paramount. It makes reviewing PR easier, it makes coming back to the code after 18 months easier, it makes your peers like you more.&lt;/p&gt;&#xA;&lt;h3 id=&#34;anti-gossip&#34;&gt;Anti-Gossip&lt;/h3&gt;&#xA;&lt;p&gt;Constructive conversations over background criticism. Call it out when you see it (even if in other parts of the company). If you feel the need to complain, make a difference and give feedback instead.&lt;/p&gt;&#xA;&lt;h3 id=&#34;approachable&#34;&gt;Approachable&lt;/h3&gt;&#xA;&lt;p&gt;During busy times, when you are deep in code and stress is mounting, it is easy to forget to Treat Others as You Would Expect to be Treated and be “approachable”. Others should not be worried about talking to you. Definitely no jerks, even if they are geniuses. Adjust your technical language when speaking to non-technical staff.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
