# Hadas Yaakobovitch's Manager Readme

**R&D Team lead at AppsFlyer**

# Motivation for this document

The creation of this doc helped me identify and refine my thoughts and values. Hopefully, this doc will help you understand me better and help us work together.

I'm looking forward to getting to know you, and this doc is not intended to replace or override the relationship and mutual understanding we will build as we work together. Its intention is to give you an idea of how I think and how I work.

# My role

In approximate order of importance:

- I am here to make sure you are both successful and happy- I want you to improve your technical skills, grow your career, enjoy your work, and believe in both our team's and company's mission.
- I am here to make sure our team is successful and pushing in the same and correct direction
- I am here to make sure our team is getting what we need from other teams, and that other teams are getting what they need from us.
- I am here to think of our next big challenge, and align it against the company's priorities.

In addition, My job is _not_ to tell you exactly what to do and how to do it, I encourage self learning and creativity. I might have thoughts on your code, and I expect you to have thoughts on mine. 

# What do I value most?

- **people first-** I believe that happy, informed, and productive people build fantastic things. 
- **Honesty-** I value transparency and honesty about  what’s happened, what’s happening, and what’s going to happen.
- **Responsibility-**  I expect you to operate as a Responsible Individual. I believe you are able to operate as a professional adult, and make smart decisions. This does not mean that I expect you to do everything on your own - I am here to provide you guidance and mentorship (either through me, or by finding the people you should be getting it from). When you need help, I expect you to not hesitate and ask for it.
- **Friendship- ** Having a good relationship and empathy for your co-workers will help us to build a strong team.
- **Constant learning- ** I value learning, and know that training up on a tech stack may not always be the fastest route to production.
- **Self criticism- ** Self criticism is an important part of growth. You’ll miss opportunities without it.  

## **You can help me by:**

- Doing amazing work. Let me know if there is something preventing you from accomplishing this.
- Telling me if you are unhappy.
- Disagreeing with me. The best solutions comes from a healthy level of debate. We need to be able to separate our ideas from our egos . I’ll challenge your ideas with the goal of coming to the best possible solution, I hope you’ll challenge mine.
- Telling me when I screw up. This is very important. I screw up and sometimes don’t notice. I need to know or I’ll likely do it again.
- Telling me when you screwed up- it's important for me to know when you've made a mistake so that the whole team could learn from it. we are all humans, we all make mistakes, but only some of us can work to prevent the same mistake from reoccurring.
- Communicating- my "door" is always open. Come to me when you have anything to say / improve / contemplate / ask.

# My Expectations

**Schedule**

I am usually in the office between 9 and 18. I am often in the office earlier or later, but with some exceptions these tend to be the hours you can count on finding me. 

As for your schedule: do what works for you, but use good judgment. If you're a night owl and you choose to work from 21 to 6, that might not work so well. But if you're a night owl who would rather be in the office closer to 11–20, or a morning person who'd rather be in closer to 7–16, that is fine with me. 

You can Slack me 24 hours a day. I like responding quickly. If I am unable to answer I will respond later, but your message will not disturb me, whenever it will reach me.

I work a bit on nights and weekends. This is my choice.  **I do not expect that you are going to work outside of work hours, unless there is something urgent.**  I might Slack you, so that the message would not be forgotten, but unless the message says URGENT, it can always wait until work begins the next day or after the weekend.

**Availability**

Some weeks, my schedule can be pretty full. Other weeks it's not so bad. If you need to chat, you have a few options.

- Catch me at my desk. If it's not a good time I will let you know.
- Slack me.
- Add a meeting in my calendar, just make sure my calendar is free that time.

**Expectations from my team-mates**

- Question everything- Be a thinker.  
- Always know why you are doing what you are doing.  
- Your code is a depiction of you, you should do your best to perfect it.  
- Respect my and your team-mate's time like I/they respect yours- 
  - come prepared to code reviews and meetings.  
  - If you cannot make it to a meeting / scrum update the meeting's creator, they may want to reschedule the meeting if you cannot attend.
  - Come to meetings on time. 

- Have a "big head"- find the "grey" areas and try to fill the gaps.

**My definition of "done"**

A project is done once it is in production and fully tested

**My definition of a failure**

- Production revert due to negligence.
- A feature coming back from QA because the basic core goals of the project were not met.

# Meetings

**1:1's**

We’ll have a 1:1 weekly for at least 30 minutes no matter what. This meeting will be split into two- half for weekly plan, and half to discuss technical ideas or issues. This meeting will cover topics of substance. I will bring a topic for each meeting, but encourage you to bring your own topic to discuss, or things you would like to deepen in.

If needed, I will give you feedback on how you're doing in our 1:1. If I'm worried about your performance, I will let you know. If you worry that I'm worried about your performance, please let me know.

**Team meetings**

We'll have an team/domain group meeting weekly for 60 minutes. Feel free to add to the calendar invite if you wish to speak or present something you have learned or have been working on, I will encourage you to do that. Similar to 1:1s, we aren’t discussing status at this meeting, but issues of substance that affect the whole team.

**Daily Scrums**

Our team has a daily scrum each day from 10:15-10:25. The scrum is a quick standup meeting where each person briefly says what he / she is working on and if something is preventing him / her from succeeding in the current task. We will share important updates during this time.

# Personality quirks

**I am best at mornings** , having a tougher time being creative during the evening- If I delay the answer to a question or challenge to the next morning know it is nothing personal. 

I sometimes talk about a task when I am still brainstorming it.  **When I ask you to do something that feels poorly defined**  you should ask me for clarification. 

# Where to focus on your first 90 days?

**Software** - The biggest thing is getting to know the ecosystem: source code, dev environment, build process and testing environments. Learn the full process from changing code all the way until it gets to production.

**Product** - The next biggest thing is getting to know the product: who uses it, why do they use it, what do they like and dislike about it, how do they report bugs and request new features. Every decision you make about the software ultimately must be informed by how it impacts users. Along with this: what is the design philosophy of the product as it stands now? What big decisions were made in the past that you have to maintain consistency with? Sometimes users will never be happy because they want an airplane and your product is a submarine. Thus, not every feature request should be fulfilled. But you have to have a basis for deciding which it is.

**Friendships** -  along the way you will form relationships with your co-workers. Not just developers but also management, CSM, marketing, IT, and support. Remember we are with these people more hours than anyone else during our employment period, it will benefit us greatly if we  will have a strong social circle at work.

Excited towards getting to know you and working together,

Hadas