# Brendan Caffrey's Manager Readme

**Engineering Director at Litmus Software, Inc.**

# What is this?

Writing software can be really really difficult.  Let's not compound that complexity with uncertain expectations and the uneasiness that can arise from working with new people.  This document will try to clear the air and level set.

# My role

I self-describe as a builder of products, processes and teams.  I view that as a natural extension of my origins as a software engineer.  My primary responsibility is to _build value_ for the organization.  Sometimes that value is in products - more often it's in building the processes and teams that builds, supports and brings those products to market.  

That's where you come in!  Day to day my role is to make you the most productive and happy you can be.  

# What do I value most?

_I value honesty and humility._  We're all amateurs at this and trying to figure out the best way forward together.  Most questions have several right answers.  We all make mistakes.  That's ok, expected even.  When you're wrong admit it and move on.  I'll work to do the same.

_Bias to action._  I tend to favor the premise of "ask for forgiveness not for permission", within reason.  Bring me solutions and ideas, not only problems.  But by all means, do bring me problems.  

# My Expectations

We're globally distributed so it's not material to me if you prefer to work 8-4, 9-5, 12-8.  Just try to be consistent and make sure your teammates and other co-workers you're working with know when you'll be available and keep your commitments to meetings.  

_Over-communicate._  Communication is important in any organization.  In remote organizations it's even more important.  Let your teammates know where you're at - success and failures.  If I need to chase you for the status of something then this system has broken down.

_Value quality.  _You understand it's not only important that something "works" but that it's also done the right way.  I value readable, testable code above clever hacks.  You're not just writing code for you but for your team.

_Be considerate._  When dealing with coworkers or other colleagues, practice thoughtful and considerate communications.  Default to being kind and helpful above all else.  We're all on the same team.    

# 1:1s

I meet weekly with direct reports for 1:1s.  I may have some things to discuss with you but ultimately this is your time to talk about whatever you want to talk about - specific struggles with project work, questions about strategy or tactics, questions or concerns about personal, team or company goals, etc.

I try hard to make sure we do chat once a week.  Even if it's just a 5 minutes "alls good" kind of chat.  

# Personality quirks

I have high expectations of myself and will frequently, unfairly and unintentionally assign those expectations to others.  This leads me to not be effusive with praise and occasionally be over critical.  Please call me out on this.  

I don't personally value "atta boys" or "good job" platitudes.  That doesn't mean I don't value you or your work.  I absolutely do.

I can be disorganized and am perpetually multitasking.  It may seem like I'm too busy to be interrupted.  That's almost never actually the case.  

# Where to focus on your first 90 days?

If you're just getting started with Litmus, welcome!  Now exhale.  There will be a lot to take in these first 90 days.  Don’t worry about understanding everything all at once. 

Be attentive, curious, active. Meet everyone on our team - and get to know your own team - by attending meetings, asking questions, involving yourself in GitHub PRs & Slack discussions.

Immerse yourself in the larger Litmus & email culture; read the blog, watch some webinars, and join some social Slack channels!