<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Management on about:rileycsillag fka drewcsillag</title>
		<link>https://riley.thecsillags.com/categories/management/</link>
		<description>Recent content in Management on about:rileycsillag fka drewcsillag</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 29 Mar 2025 12:00:00 -0400</lastBuildDate>
		
			<atom:link href="https://riley.thecsillags.com/categories/management/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Presentation: Non-technical Guide To Technical Leadership</title>
				<link>https://riley.thecsillags.com/posts/2025-03-15-non-technical-guide-to-techic/</link>
				<pubDate>Sat, 29 Mar 2025 12:00:00 -0400</pubDate>
				<guid>https://riley.thecsillags.com/posts/2025-03-15-non-technical-guide-to-techic/</guid>
				<description>&lt;p&gt;This is a presentation I&amp;rsquo;ve done now about six times, starting back about 6 years ago. It stemmed from seeing people new to being a tech-lead on a team (either as manager or not) and what were the common pitfalls they fell into. So without further ado, the talk.&lt;/p&gt;&#xA;&lt;!-- more --&gt;&#xA;&lt;p&gt;Hi and welcome to the non-technical guide to technical leadership!&lt;/p&gt;&#xA;&lt;p&gt;One preface here before we start, I refer to the role of tech lead (or TL) often in this talk, but to be clear, the tech lead is a role, not a title. You may be an engineer, or a manager. Basically, any project which you are responsible for driving technical decisions on, you are the TL.&lt;/p&gt;</description>
			</item>
			<item>
				<title>My Contract To My Team</title>
				<link>https://riley.thecsillags.com/posts/2025-02-27-contract-to-the-team/</link>
				<pubDate>Thu, 27 Feb 2025 12:00:00 -0400</pubDate>
				<guid>https://riley.thecsillags.com/posts/2025-02-27-contract-to-the-team/</guid>
				<description>&lt;p&gt;When I switched to management last year on April 5, one of the things I wanted to start with was&#xA;to make sure that my teams understood what they could expect from me and hold me to. I had been at the company for&#xA;over three years and interacted with many of them before, so I wasn&amp;rsquo;t a stranger, but one thing I&amp;rsquo;ve learned is that&#xA;clarity rarely hurts in situations like these. And so I wrote up a &amp;ldquo;contract&amp;rdquo; of what they could expect from me. I later&#xA;updated it to be what they could expect from the managers that report up to me as well, including things like PTO, sick time,&#xA;not micromanaging, and so on.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
