# Luke Stringer's Manager Readme

**Principal Consultant at Hippo Digital**

# Motivation for this document

There is a good chance you are reading this document because we are working together in a team, or we will be doing so at some point in the future. We may be colleagues in similar roles, or I might be your tech lead or manager. This document aims to provide an overview of how best to work with me. I’ll explain what my current role entails, what I value and expect from others, and in turn what you can expect from me.

# My Background

My technical background is in mobile development, specifically native iOS development. I started building apps around 2009 with the iPhone OS 3 SDK. I’ve written apps with Objective-C and Swift, using both UIKit and SwiftUI. I’ve also worked closely with native Android, React Native and Flutter engineers, and although I haven't shipped my own production code with these frameworks, I have a good grasp of what they entail. 

One technical subject I try to maintain expertise in is version control with Git. (Past colleagues have noted that I was at my happiest when I was drawing a branching diagram.) If you want some support with using Git, whether it's resolving merge conflicts, undoing an error, or just trying to figure out what could have caused a weird problem, I’m always happy to assist.

Along with my direct experience of writing code, I have also spent roughly half of my career doing “people things”. Whether this is Engineering Management, Line Management, or Technical Leadership on a project, I’m comfortable fulfilling roles that do not involve significant programming duties. I enjoy these roles for the variety of experience they bring. 

I try to keep my hands warm (rather than being “hands on”) with the development side of a project. I like to know how to run and execute the code on my own machine, have a general understanding of an application’s code structure, and feel comfortable reviewing code. This might mean I ask what seem straightforward or beginner-level questions, but I believe that knowing about the code makes me a better technical leader. Moreover, I hope that normalising the asking of (potentially) obvious questions makes it more acceptable for others to do the same. 

If I have an area of technical ignorance, I try to use this to my advantage, allowing me to ask simple / obvious / difficult  questions to create a shared understanding across a team.

# My Role

At Hippo Digital, I am a Principal Software Consultant. 

# My Expectations

Above all, I value honesty and openness. If you have something on your mind, whether big or small, I’d like to hear about it. 

In turn, I will endeavour to be honest and open with you as well. I’ll do my best to be as transparent as possible with my own work and the information I have access to. This means you are free to ask me questions on any topic. I will also provide information voluntarily and proactively if I think you will benefit from it. 

Please remember that in a leadership role, I often have to be careful with sensitive or private information, so if I omit anything from our conversation, it could be for these reasons. Information can sometimes be unclear, ambiguous, or even confusing, so I will do my best to provide extra context in these situations. However, if you prefer not to know this sort of information, please say so. I get that some people want to be heads down in their own work (ignorance is bliss, etc), so please set these expectations with me.

If we work together on a plan to solve a problem, whether technical or otherwise, I commit to following through on my actions. Similarly, I expect you to follow through on what we have agreed. I will hold you accountable for this, and I expect you to do the same for me as well. 

# How I Communicate

I am comfortable with all forms of communication and happy to adapt to whichever style suits you and the situation best. 

Sometimes asynchronous communication (not in real time, like Slack chats) works well for certain non-critical conversations. However, I know that instant messages can miss a lot of nuance, are often inadequate for making a timely decision, and therefore it can be just as easy to schedule a meeting or ask for a quick call. 

For instant message communication, I prefer to type in full sentences, in a style not dissimilar to this document. I am not the most precise typist, nor are my spelling and grammar the most correct. If something is unclear, please point it out; I will not be offended. 

When first starting a chat, I ask how you are doing before jumping straight into work topics. I also make generous use of emojis to express myself and add colour to my discussions. I have no expectation you follow this same style. So long as you communicate as clearly and authentically as possible, then that is fine with me. 

I do have one hard rule for instant messaging: avoid sending me just a “Hello” message. Although a normal thing to say in person, receiving this asynchronously can be disruptive as it omits the content of what you want to talk about, and I have to wait for your follow-up message. I’m not alone in feeling this way, so [please don’t say just hello](https://nohello.net/en). Thanks in advance 😊

# How I do Meetings

When inviting you to a meeting I will set an appropriate title and agenda so it is clear why I need your attendance. Even if the purpose is for a quick follow-up chat, saying so in the invite helps to set expectations so everyone can prepare. In turn, I expect you to also follow the same etiquette. There’s nothing worse than getting a “Quick chat” meeting invitation out of the blue. The uncertainty is hard to prepare for, so be kind to attendees and tell them where you need their time. A simple rule to remember is “No agenda, then no attenda”.

If we are meeting remotely, I will put my webcam on, and, if possible, I would prefer that you do the same. This helps us both engage with the conversation, which when conducted remotely can be harder than in person. If there is a reason why you do not wish to use your webcam, please say so at the start of the meeting as this avoids awkward “can you put your webcam on please?” questions. 

I take handwritten notes during meetings. This is because my typing is quite poor (see above) and I am simply quicker with pen and paper. I use a four-colour pen, which gives me [just enough formatting options to be effective](https://marcgg.com/blog/2017/10/09/paper-note-taking-meetings/), without becoming overwhelmed with the options that most digital tools provide. 

During a meeting, I tend to ask quite a few follow-up questions. This helps me structure information so I can process it and understand the next steps. I’ll try my best to understand your point of view, and play this back to you to confirm I have it right. 

I have a strong preference for visualising a problem with diagrams. If we are chatting in person, I’ll often reach for pen and paper, or even better a whiteboard, to externalise what I am thinking. If we are remote, I like to use a Miro board,  or an equivalent tool. I find that a handful of boxes, lines, and arrows can save a lot of time that would otherwise be wasted on poorly describing things with words, or even worse, leaving a conversation without a shared understanding. Please contribute to these sketches without feeling self-conscious; I am certainly no artist, and my handwriting leaves a lot to be desired!

# My Work Hours

My work hours are normally between 09:00 and 17:00. Where these vary, I will give you as much notice as possible, and amend my Slack status as appropriate. 

I try my very best not to make a habit of checking in on work things outside of these hours to maintain a healthy work/life balance. If you do need to contact me outside of work hours, then a text message or phone call to my personal number is the best method. 

Similarly, I will not contact you outside your working hours. If we are working at different times and I need to send you a message, I have no expectation of receiving a reply until you are back at work. 

# My Personality Quirks

I try not to take myself too seriously. I love a good "dad joke", and puns and silly cultural references come par for the course when working with me. I embrace the goofy side of my personality, and I am more than happy for people to do the same. 

In conversation, I often make use of metaphors and idioms. When done right, I hope this means I am a more effective communicator. However, if something is not straightforward to understand, please say so.