# Sators's Manager Readme

**CTO at Mosaic**

# Motivation

Welcome to my User Guide to Working with Sators! My goal is to document the unspoken thoughts, expectations, objectives, and personality attributes so others can have better insight into what drives me.&nbsp;&nbsp;I offer this to you because I recognize that the faster we get to know each other and how we work, the better and stronger our relationship will be, and the more we’ll accomplish together.

# My Role

In a nutshell, my efforts are both short-term and long-term - producing quality code, reviewing and guiding the output of other developers, and strategizing the future features and development of the platform through efficient communication, effective development, and optimized workflows.

My skill set is hard to contain in a single title.&nbsp; My role primarily includes leading the developer team,&nbsp;brainstorming and architecting, code review,&nbsp;and coding in TypeScript/JavaScript/Python.&nbsp; Furthermore, I am responsible for the company's cloud server infrastructure and AWS environment.&nbsp; Finally, I lead the charge of being a ScrumMaster for our team's sprint ceremonies.

Our team is measured by delivering a quality product for our users.&nbsp; This is achieved by thorough planning and strategic execution, and a close examination of the quality of our final result.

I love to see people grow and thrive, and I enjoy being part of that process.&nbsp; I am not satisfied with the status quo and challenge myself to be open to refining the process for providing improvement in all aspects.&nbsp;

# My Values

My highest value is a quality result, with a clean and efficient codebase.&nbsp; I want to be able to review code, understand its intent and objective, either via the code itself or comments/documentation, and I don't want to see repetition.&nbsp;&nbsp;

The best form of correction is the truth.&nbsp; If I see an issue or am experiencing frustration, I challenge myself to address that sooner than later.&nbsp; The juxtaposition to that is that I am a strong optimist.&nbsp; The glass is always half full, and the sun will come out tomorrow.&nbsp; This likely leads to my greatest weakness of being blind to how serious an issue might actually be.&nbsp; Being confronted with reality helps bring me down to earth.

# My Expectations

In general, I support you working during the hours that you work the best.&nbsp; That being said, there are some group meetings that you are expected to attend.&nbsp; My preferred means of communication is Slack.&nbsp;&nbsp;

I expect a daily&nbsp;"check-in" as our form of daily standup.&nbsp; This should at minimum be what you did the day before and what is on your plate for the day.&nbsp;

We'll have a weekly 1:1 (see below), however, I'm always happy to&nbsp;connect to go over additional items -&nbsp;hit me up on Slack to potentially connect on Zoom if needed.&nbsp;&nbsp;

Mistakes happen.&nbsp; That's how we grow.&nbsp; My objective is for us to all learn from our mistakes, both our own and others.&nbsp; It is not the objective to have a blame culture, but I encourage us to share mistakes so that we can become stronger together.

# 1:1s

An official 1:1 meeting will be on our calendars once a week.&nbsp; My goal is to be laser-focused on you and our time together with notifications disabled.&nbsp;&nbsp;This time is yours and I encourage you to bring an agenda, list of questions, topics,&nbsp;etc.&nbsp; It will also be a time that I might go over any business/housekeeping updates.&nbsp; This time also serves as an opportunity for addressing any concerns/frustrations/performance reviews/etc, both those that I may have for you, but also those you might have for me or the company&nbsp;as well.&nbsp;&nbsp;

If you are hitting a brick wall or need clarification on work, please do not feel like you have to wait for our 1:1 scheduled meeting.&nbsp; Reach out at any time for answers to questions, clarification, or peer coding to ensure you are on the right track.

# Personality Quirks / Hobbies

As previously mentioned, I am an optimist - potentially to a fault.&nbsp; I believe that I am a patient person, and am tough to disappoint...but I really don't like having to repeat myself.

I am passionate about&nbsp;cleanliness and organization - well-documented, readable, and reusable&nbsp;code will light up my day.&nbsp; The opposite is also true - disorganization, messy code, poorly named variables, improper indentation, etc are nails on a chalkboard.

I strive to work smarter, not harder, so any efficiency boosts or time-saving tricks are also right up my alley.

When you enjoy what you do for your job, it doesn't feel like work.&nbsp; I love to code, and I love teaching/helping others - so you'll often find me either coding or tutoring other developers in my non-work hours.&nbsp; Other than that, I enjoy being a private pilot and flying as well as woodworking.&nbsp; During the summer months you'll find me playing ultimate frisbee, camping, and spending time outside.

# Where to focus on your first 90 days?

Comprehension.&nbsp; Our team works with existing codebases, as well as new efforts/projects.&nbsp; Therefore, gaining context and understanding of our strategies is key for being able to contribute effectively.

In order to achieve this, ask questions...lots of questions - but try not to have to ask the same questions over and over.&nbsp; Everyone on the team, especially myself,&nbsp;wants you to succeed and is ready and willing to help answer any questions you might have.&nbsp; I would recommend taking notes of the answers to questions&nbsp;and reviewing those notes accordingly.

The measure of success in your first 30 days will be how your pull requests go.&nbsp; Granted, all of us still occasionally&nbsp;put up PRs that end up with rounds of issues.&nbsp; Ideally, the diff that&nbsp;your PRs are requesting will be limited to only containing the changes necessary to complete the tasks within the scope of the story.