Hi! Welcome to the team, I'm very happy to have you here, and I'm sure we will build amazing things together. You are now starting a new chapter in your career in our company, this is the time for you to take a listen, write things down, ask any question that comes to your mind and get to know the team and company.
I believe every complex piece of code should be properly documented, so it would be easier to understand and maintain. Humans are even more complex than any piece of code you can find, so why not have documentation to help people interact with each other better? This is my documentation for you :).
I'm Moshiko 28yo, I'm T1D since I was 11yo,
I started my SW career at the Israeli ministry of defense, where I served as a software developer for couple of years.
Then I joined a company called DreaMed Diabetes, I started there as a junior SW developer and worked my way up to be a software team leader.
I'm an off-road driver, motor lover, and an amateur photographer.
My Role is divided into three sections:
- People role - As a manager, my role is to make the team (and you :)) move faster and more efficiently.
I will be here to mentor, help you grow, develop your talent, and reach your goals. As a part of my role, I will provide you with context on your tasks, and I will be your point of contact for anything (good or bad) you want to share with the management team. - Tech role - It is my responsibility to make sure we are building an amazing, scalable, and maintainable product. As part of this responsibility, I would ensure your code is developed according to company standards, code conventions, and business requirements. I will be here to answer any tech/architecture questions you may have.
- Product role - As a part of being a manager, my job is to understand the company product and provide clear business context whenever needed.
That would allow you to design and implement better-suited solutions for the task.
- End-to-end Ownership - When you get a new task, I expect you to understand the full context of the mission. Understanding the full context (tech and product) can bring up solutions or issues that will affect the feature development and help us build a better product for our customers.
- Be A Team Player - Conflicts and bugs are part of a programmer's job. When such a thing happens, I need you to remember no one is looking for someone to blame. We are all in the same boat that needs to be steered together to the best land we can find. If someone did wrong, we will help him/her fix and learn from the mistake.
- Boy\Girl Scout Rule - There are some rules that I follow, one of them is the "Boy\Girl Scout Rule".
This is a rule taken from the US Boy Scouts, and it goes like this:
When the Boy Scouts leave a camping zone, they leave the place cleaner than before.
When you get a task in the codebase, I expect you to leave it cleaner than it was when you got it. This would make our codebase cleaner with every feature we add. - Continues Improvement - I believe that each one of us, and the team as a whole, should be in a process of "Continues Improvement" at all times, which means every feedback, suggestion, comment, you have to me, or to any team process, I would be more than happy to hear it and take it under consideration.
- I argue with “passion” - I may raise my voice a little. I don’t like it about myself, and I try to improve. That may happen because I like the product, and it's important to me to make sure we do it as good as we can. If you feel I crossed the line, please let me know. It’s not my intent.
- I have the memory and attention span of a goldfish - The only way I can be productive is by constantly taking notes. If you see me typing while we're talking, I'm not browsing Facebook, just trying to record what we're saying so I can reflect and process it later on.
1:1s are your meetings. This is your place to talk about anything that's bothering you or you want to share. Those meetings won't be about status updates, we would talk about your career goals and how we can help you achieve them. For us to be productive in our 1:1s, I would like you to be prepared: prepare questions, suggestions, initiativs, thoughts, feedbacks, or any other agenda. But don't worry, if you won't, I will navigate the conversation :).